€•ø^Œsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ#/translations/zh_CN/trace/mmiotrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/zh_TW/trace/mmiotrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/it_IT/trace/mmiotrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/ja_JP/trace/mmiotrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/ko_KR/trace/mmiotrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/pt_BR/trace/mmiotrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ#/translations/sp_SP/trace/mmiotrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ#In-kernel memory-mapped I/O tracing”h]”hŒ#In-kernel memory-mapped I/O tracing”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³Œ=/var/lib/git/docbuild/linux/Documentation/trace/mmiotrace.rst”h´KubhŒ paragraph”“”)”}”(hŒ1Home page and links to optional user space tools:”h]”hŒ1Home page and links to optional user space tools:”…””}”(hhÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubhŒ block_quote”“”)”}”(hŒ/https://nouveau.freedesktop.org/wiki/MmioTrace ”h]”hÌ)”}”(hŒ.https://nouveau.freedesktop.org/wiki/MmioTrace”h]”hŒ reference”“”)”}”(hhãh]”hŒ.https://nouveau.freedesktop.org/wiki/MmioTrace”…””}”(hhçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”hãuh1håhháubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KhhÝubah}”(h]”h ]”h"]”h$]”h&]”uh1hÛh³hÊh´Khh·h²hubhÌ)”}”(hXMMIO tracing was originally developed by Intel around 2003 for their Fault Injection Test Harness. In Dec 2006 - Jan 2007, using the code from Intel, Jeff Muizelaar created a tool for tracing MMIO accesses with the Nouveau project in mind. Since then many people have contributed.”h]”hXMMIO tracing was originally developed by Intel around 2003 for their Fault Injection Test Harness. In Dec 2006 - Jan 2007, using the code from Intel, Jeff Muizelaar created a tool for tracing MMIO accesses with the Nouveau project in mind. Since then many people have contributed.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hh·h²hubhÌ)”}”(hŒ©Mmiotrace was built for reverse engineering any memory-mapped IO device with the Nouveau project as the first real user. Only x86 and x86_64 architectures are supported.”h]”hŒ©Mmiotrace was built for reverse engineering any memory-mapped IO device with the Nouveau project as the first real user. Only x86 and x86_64 architectures are supported.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubhÌ)”}”(hŒxOut-of-tree mmiotrace was originally modified for mainline inclusion and ftrace framework by Pekka Paalanen .”h]”(hŒmOut-of-tree mmiotrace was originally modified for mainline inclusion and ftrace framework by Pekka Paalanen <”…””}”(hjh²hh³Nh´Nubhæ)”}”(hŒ pq@iki.fi”h]”hŒ pq@iki.fi”…””}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:pq@iki.fi”uh1håhjubhŒ>.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubh¶)”}”(hhh]”(h»)”}”(hŒ Preparation”h]”hŒ Preparation”…””}”(hjBh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj?h²hh³hÊh´KubhÌ)”}”(hXÏMmiotrace feature is compiled in by the CONFIG_MMIOTRACE option. Tracing is disabled by default, so it is safe to have this set to yes. SMP systems are supported, but tracing is unreliable and may miss events if more than one CPU is on-line, therefore mmiotrace takes all but one CPU off-line during run-time activation. You can re-enable CPUs by hand, but you have been warned, there is no way to automatically detect if you are losing events due to CPUs racing.”h]”hXÏMmiotrace feature is compiled in by the CONFIG_MMIOTRACE option. Tracing is disabled by default, so it is safe to have this set to yes. SMP systems are supported, but tracing is unreliable and may miss events if more than one CPU is on-line, therefore mmiotrace takes all but one CPU off-line during run-time activation. You can re-enable CPUs by hand, but you have been warned, there is no way to automatically detect if you are losing events due to CPUs racing.”…””}”(hjPh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj?h²hubeh}”(h]”Œ preparation”ah ]”h"]”Œ preparation”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒUsage Quick Reference”h]”hŒUsage Quick Reference”…””}”(hjih²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjfh²hh³hÊh´K#ubhŒ literal_block”“”)”}”(hX&$ mount -t debugfs debugfs /sys/kernel/debug $ echo mmiotrace > /sys/kernel/tracing/current_tracer $ cat /sys/kernel/tracing/trace_pipe > mydump.txt & Start X or whatever. $ echo "X is up" > /sys/kernel/tracing/trace_marker $ echo nop > /sys/kernel/tracing/current_tracer Check for lost events.”h]”hX&$ mount -t debugfs debugfs /sys/kernel/debug $ echo mmiotrace > /sys/kernel/tracing/current_tracer $ cat /sys/kernel/tracing/trace_pipe > mydump.txt & Start X or whatever. $ echo "X is up" > /sys/kernel/tracing/trace_marker $ echo nop > /sys/kernel/tracing/current_tracer Check for lost events.”…””}”hjysbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1jwh³hÊh´K&hjfh²hubeh}”(h]”Œusage-quick-reference”ah ]”h"]”Œusage quick reference”ah$]”h&]”uh1hµhh·h²hh³hÊh´K#ubh¶)”}”(hhh]”(h»)”}”(hŒUsage”h]”hŒUsage”…””}”(hj”h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj‘h²hh³hÊh´K0ubhÌ)”}”(hŒVMake sure debugfs is mounted to /sys/kernel/debug. If not (requires root privileges)::”h]”hŒUMake sure debugfs is mounted to /sys/kernel/debug. If not (requires root privileges):”…””}”(hj¢h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K2hj‘h²hubjx)”}”(hŒ,$ mount -t debugfs debugfs /sys/kernel/debug”h]”hŒ,$ mount -t debugfs debugfs /sys/kernel/debug”…””}”hj°sbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´K5hj‘h²hubhÌ)”}”(hŒ;Check that the driver you are about to trace is not loaded.”h]”hŒ;Check that the driver you are about to trace is not loaded.”…””}”(hj¾h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K7hj‘h²hubhÌ)”}”(hŒ/Activate mmiotrace (requires root privileges)::”h]”hŒ.Activate mmiotrace (requires root privileges):”…””}”(hjÌh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K9hj‘h²hubjx)”}”(hŒ5$ echo mmiotrace > /sys/kernel/tracing/current_tracer”h]”hŒ5$ echo mmiotrace > /sys/kernel/tracing/current_tracer”…””}”hjÚsbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´K;hj‘h²hubhÌ)”}”(hŒStart storing the trace::”h]”hŒStart storing the trace:”…””}”(hjèh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K=hj‘h²hubjx)”}”(hŒ3$ cat /sys/kernel/tracing/trace_pipe > mydump.txt &”h]”hŒ3$ cat /sys/kernel/tracing/trace_pipe > mydump.txt &”…””}”hjösbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´K?hj‘h²hubhÌ)”}”(hŒCThe 'cat' process should stay running (sleeping) in the background.”h]”hŒGThe ‘cat’ process should stay running (sleeping) in the background.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KAhj‘h²hubhÌ)”}”(hŒLoad the driver you want to trace and use it. Mmiotrace will only catch MMIO accesses to areas that are ioremapped while mmiotrace is active.”h]”hŒLoad the driver you want to trace and use it. Mmiotrace will only catch MMIO accesses to areas that are ioremapped while mmiotrace is active.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KChj‘h²hubhÌ)”}”(hXDuring tracing you can place comments (markers) into the trace by $ echo "X is up" > /sys/kernel/tracing/trace_marker This makes it easier to see which part of the (huge) trace corresponds to which action. It is recommended to place descriptive markers about what you do.”h]”hXDuring tracing you can place comments (markers) into the trace by $ echo “X is up†> /sys/kernel/tracing/trace_marker This makes it easier to see which part of the (huge) trace corresponds to which action. It is recommended to place descriptive markers about what you do.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KFhj‘h²hubhÌ)”}”(hŒ0Shut down mmiotrace (requires root privileges)::”h]”hŒ/Shut down mmiotrace (requires root privileges):”…””}”(hj.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KLhj‘h²hubjx)”}”(hŒ/$ echo nop > /sys/kernel/tracing/current_tracer”h]”hŒ/$ echo nop > /sys/kernel/tracing/current_tracer”…””}”hj<sbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´KNhj‘h²hubhÌ)”}”(hŒ]The 'cat' process exits. If it does not, kill it by issuing 'fg' command and pressing ctrl+c.”h]”hŒeThe ‘cat’ process exits. If it does not, kill it by issuing ‘fg’ command and pressing ctrl+c.”…””}”(hjJh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KPhj‘h²hubhÌ)”}”(hŒMCheck that mmiotrace did not lose events due to a buffer filling up. Either::”h]”hŒLCheck that mmiotrace did not lose events due to a buffer filling up. Either:”…””}”(hjXh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KShj‘h²hubjx)”}”(hŒ$ grep -i lost mydump.txt”h]”hŒ$ grep -i lost mydump.txt”…””}”hjfsbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´KUhj‘h²hubhÌ)”}”(hŒ;which tells you exactly how many events were lost, or use::”h]”hŒ:which tells you exactly how many events were lost, or use:”…””}”(hjth²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KWhj‘h²hubjx)”}”(hŒ$ dmesg”h]”hŒ$ dmesg”…””}”hj‚sbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´KYhj‘h²hubhÌ)”}”(hŒîto view your kernel log and look for "mmiotrace has lost events" warning. If events were lost, the trace is incomplete. You should enlarge the buffers and try again. Buffers are enlarged by first seeing how large the current buffers are::”h]”hŒñto view your kernel log and look for “mmiotrace has lost events†warning. If events were lost, the trace is incomplete. You should enlarge the buffers and try again. Buffers are enlarged by first seeing how large the current buffers are:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K[hj‘h²hubjx)”}”(hŒ($ cat /sys/kernel/tracing/buffer_size_kb”h]”hŒ($ cat /sys/kernel/tracing/buffer_size_kb”…””}”hjžsbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´K`hj‘h²hubhÌ)”}”(hŒVgives you a number. Approximately double this number and write it back, for instance::”h]”hŒUgives you a number. Approximately double this number and write it back, for instance:”…””}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kbhj‘h²hubjx)”}”(hŒ2$ echo 128000 > /sys/kernel/tracing/buffer_size_kb”h]”hŒ2$ echo 128000 > /sys/kernel/tracing/buffer_size_kb”…””}”hjºsbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´Kehj‘h²hubhÌ)”}”(hŒThen start again from the top.”h]”hŒThen start again from the top.”…””}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kghj‘h²hubhÌ)”}”(hŒ{If you are doing a trace for a driver project, e.g. Nouveau, you should also do the following before sending your results::”h]”hŒzIf you are doing a trace for a driver project, e.g. Nouveau, you should also do the following before sending your results:”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kihj‘h²hubjx)”}”(hŒq$ lspci -vvv > lspci.txt $ dmesg > dmesg.txt $ tar zcf pciid-nick-mmiotrace.tar.gz mydump.txt lspci.txt dmesg.txt”h]”hŒq$ lspci -vvv > lspci.txt $ dmesg > dmesg.txt $ tar zcf pciid-nick-mmiotrace.tar.gz mydump.txt lspci.txt dmesg.txt”…””}”hjäsbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´Klhj‘h²hubhÌ)”}”(hŒ¼and then send the .tar.gz file. The trace compresses considerably. Replace "pciid" and "nick" with the PCI ID or model name of your piece of hardware under investigation and your nickname.”h]”hŒÄand then send the .tar.gz file. The trace compresses considerably. Replace “pciid†and “nick†with the PCI ID or model name of your piece of hardware under investigation and your nickname.”…””}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kphj‘h²hubeh}”(h]”Œusage”ah ]”h"]”Œusage”ah$]”h&]”uh1hµhh·h²hh³hÊh´K0ubh¶)”}”(hhh]”(h»)”}”(hŒHow Mmiotrace Works”h]”hŒHow Mmiotrace Works”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´KvubhÌ)”}”(hXvAccess to hardware IO-memory is gained by mapping addresses from PCI bus by calling one of the ioremap_*() functions. Mmiotrace is hooked into the __ioremap() function and gets called whenever a mapping is created. Mapping is an event that is recorded into the trace log. Note that ISA range mappings are not caught, since the mapping always exists and is returned directly.”h]”hXvAccess to hardware IO-memory is gained by mapping addresses from PCI bus by calling one of the ioremap_*() functions. Mmiotrace is hooked into the __ioremap() function and gets called whenever a mapping is created. Mapping is an event that is recorded into the trace log. Note that ISA range mappings are not caught, since the mapping always exists and is returned directly.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kxhjh²hubhÌ)”}”(hXNMMIO accesses are recorded via page faults. Just before __ioremap() returns, the mapped pages are marked as not present. Any access to the pages causes a fault. The page fault handler calls mmiotrace to handle the fault. Mmiotrace marks the page present, sets TF flag to achieve single stepping and exits the fault handler. The instruction that faulted is executed and debug trap is entered. Here mmiotrace again marks the page as not present. The instruction is decoded to get the type of operation (read/write), data width and the value read or written. These are stored to the trace log.”h]”hXNMMIO accesses are recorded via page faults. Just before __ioremap() returns, the mapped pages are marked as not present. Any access to the pages causes a fault. The page fault handler calls mmiotrace to handle the fault. Mmiotrace marks the page present, sets TF flag to achieve single stepping and exits the fault handler. The instruction that faulted is executed and debug trap is entered. Here mmiotrace again marks the page as not present. The instruction is decoded to get the type of operation (read/write), data width and the value read or written. These are stored to the trace log.”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K~hjh²hubhÌ)”}”(hŒûSetting the page present in the page fault handler has a race condition on SMP machines. During the single stepping other CPUs may run freely on that page and events can be missed without a notice. Re-enabling other CPUs during tracing is discouraged.”h]”hŒûSetting the page present in the page fault handler has a race condition on SMP machines. During the single stepping other CPUs may run freely on that page and events can be missed without a notice. Re-enabling other CPUs during tracing is discouraged.”…””}”(hj5h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K‡hjh²hubeh}”(h]”Œhow-mmiotrace-works”ah ]”h"]”Œhow mmiotrace works”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kvubh¶)”}”(hhh]”(h»)”}”(hŒTrace Log Format”h]”hŒTrace Log Format”…””}”(hjNh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjKh²hh³hÊh´KŽubhÌ)”}”(hX"The raw log is text and easily filtered with e.g. grep and awk. One record is one line in the log. A record starts with a keyword, followed by keyword- dependent arguments. Arguments are separated by a space, or continue until the end of line. The format for version 20070824 is as follows:”h]”hX"The raw log is text and easily filtered with e.g. grep and awk. One record is one line in the log. A record starts with a keyword, followed by keyword- dependent arguments. Arguments are separated by a space, or continue until the end of line. The format for version 20070824 is as follows:”…””}”(hj\h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KhjKh²hubeh}”(h]”Œtrace-log-format”ah ]”h"]”Œtrace log format”ah$]”h&]”uh1hµhh·h²hh³hÊh´KŽubh¶)”}”(hhh]”(h»)”}”(hŒ1Explanation Keyword Space-separated arguments”h]”hŒ1Explanation Keyword Space-separated arguments”…””}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjrh²hh³hÊh´K–ubhÌ)”}”(hX!read event R width, timestamp, map id, physical, value, PC, PID write event W width, timestamp, map id, physical, value, PC, PID ioremap event MAP timestamp, map id, physical, virtual, length, PC, PID iounmap event UNMAP timestamp, map id, PC, PID marker MARK timestamp, text version VERSION the string "20070824" info for reader LSPCI one line from lspci -v PCI address map PCIDEV space-separated /proc/bus/pci/devices data unk. opcode UNKNOWN timestamp, map id, physical, data, PC, PID”h]”hX%read event R width, timestamp, map id, physical, value, PC, PID write event W width, timestamp, map id, physical, value, PC, PID ioremap event MAP timestamp, map id, physical, virtual, length, PC, PID iounmap event UNMAP timestamp, map id, PC, PID marker MARK timestamp, text version VERSION the string “20070824†info for reader LSPCI one line from lspci -v PCI address map PCIDEV space-separated /proc/bus/pci/devices data unk. opcode UNKNOWN timestamp, map id, physical, data, PC, PID”…””}”(hjƒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K˜hjrh²hubhÌ)”}”(hX¶Timestamp is in seconds with decimals. Physical is a PCI bus address, virtual is a kernel virtual address. Width is the data width in bytes and value is the data value. Map id is an arbitrary id number identifying the mapping that was used in an operation. PC is the program counter and PID is process id. PC is zero if it is not recorded. PID is always zero as tracing MMIO accesses originating in user space memory is not yet supported.”h]”hX¶Timestamp is in seconds with decimals. Physical is a PCI bus address, virtual is a kernel virtual address. Width is the data width in bytes and value is the data value. Map id is an arbitrary id number identifying the mapping that was used in an operation. PC is the program counter and PID is process id. PC is zero if it is not recorded. PID is always zero as tracing MMIO accesses originating in user space memory is not yet supported.”…””}”(hj‘h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¢hjrh²hubhÌ)”}”(hŒŠFor instance, the following awk filter will pass all 32-bit writes that target physical addresses in the range [0xfb73ce40, 0xfb800000] ::”h]”hŒ‡For instance, the following awk filter will pass all 32-bit writes that target physical addresses in the range [0xfb73ce40, 0xfb800000]”…””}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K©hjrh²hubjx)”}”(hŒV$ awk '/W 4 / { adr=strtonum($5); if (adr >= 0xfb73ce40 && adr < 0xfb800000) print; }'”h]”hŒV$ awk '/W 4 / { adr=strtonum($5); if (adr >= 0xfb73ce40 && adr < 0xfb800000) print; }'”…””}”hj­sbah}”(h]”h ]”h"]”h$]”h&]”j‡jˆuh1jwh³hÊh´K­hjrh²hubeh}”(h]”Œ-explanation-keyword-space-separated-arguments”ah ]”h"]”Œ-explanation keyword space-separated arguments”ah$]”h&]”uh1hµhh·h²hh³hÊh´K–ubh¶)”}”(hhh]”(h»)”}”(hŒTools for Developers”h]”hŒTools for Developers”…””}”(hjÆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÃh²hh³hÊh´K²ubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hŒ±The user space tools include utilities for: - replacing numeric addresses and values with hardware register names - replaying MMIO logs, i.e., re-executing the recorded writes ”h]”(hŒterm”“”)”}”(hŒ+The user space tools include utilities for:”h]”hŒ+The user space tools include utilities for:”…””}”(hjáh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jßh³hÊh´K·hjÛubhŒ definition”“”)”}”(hhh]”hŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒCreplacing numeric addresses and values with hardware register names”h]”hÌ)”}”(hjýh]”hŒCreplacing numeric addresses and values with hardware register names”…””}”(hjÿh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kµhjûubah}”(h]”h ]”h"]”h$]”h&]”uh1jùhjöubjú)”}”(hŒ=replaying MMIO logs, i.e., re-executing the recorded writes ”h]”hÌ)”}”(hŒ;replaying MMIO logs, i.e., re-executing the recorded writes”h]”hŒ;replaying MMIO logs, i.e., re-executing the recorded writes”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¶hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jùhjöubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jôh³hÊh´Kµhjñubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhjÛubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´K·hjÖubah}”(h]”h ]”h"]”h$]”h&]”uh1jÔhjÃh²hh³Nh´Nubeh}”(h]”Œtools-for-developers”ah ]”h"]”Œtools for developers”ah$]”h&]”uh1hµhh·h²hh³hÊh´K²ubeh}”(h]”Œ#in-kernel-memory-mapped-i-o-tracing”ah ]”h"]”Œ#in-kernel memory-mapped i/o tracing”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hºNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jwŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jQjNjcj`jŽj‹jjjHjEjojljÀj½jIjFuŒ nametypes”}”(jQ‰jc‰jމj‰jH‰jo‰jÀ‰jI‰uh}”(jNh·j`j?j‹jfjj‘jEjjljKj½jrjFjÃuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.