€•³     Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ /translations/zh_CN/trace/ftrace”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ /translations/zh_TW/trace/ftrace”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ /translations/it_IT/trace/ftrace”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ /translations/ja_JP/trace/ftrace”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ /translations/ko_KR/trace/ftrace”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ /translations/pt_BR/trace/ftrace”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ /translations/sp_SP/trace/ftrace”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒftrace - Function Tracer”h]”hŒftrace - Function Tracer”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³Œ:/var/lib/git/docbuild/linux/Documentation/trace/ftrace.rst”h´KubhŒ	paragraph”“”)”}”(hŒCopyright 2008 Red Hat Inc.”h]”hŒCopyright 2008 Red Hat Inc.”…””}”(hhÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubhŒ
field_list”“”)”}”(hhh]”(hŒfield”“”)”}”(hhh]”(hŒ
field_name”“”)”}”(hŒAuthor”h]”hŒAuthor”…””}”(hhçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1håhhâh³hÊh´K ubhŒ
field_body”“”)”}”(hŒ$Steven Rostedt <srostedt@redhat.com>”h]”hÌ)”}”(hhùh]”(hŒSteven Rostedt <”…””}”(hhûh²hh³Nh´NubhŒ	reference”“”)”}”(hŒsrostedt@redhat.com”h]”hŒsrostedt@redhat.com”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:srostedt@redhat.com”uh1j  hhûubhŒ>”…””}”(hhûh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh÷ubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhhâubeh}”(h]”h ]”h"]”h$]”h&]”uh1hàh³hÊh´KhhÝh²hubhá)”}”(hhh]”(hæ)”}”(hŒLicense”h]”hŒLicense”…””}”(hj-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1håhj*  h³hÊh´K ubhö)”}”(hŒPThe GNU Free Documentation License, Version 1.2
(dual licensed under the GPL v2)”h]”hÌ)”}”(hŒPThe GNU Free Documentation License, Version 1.2
(dual licensed under the GPL v2)”h]”hŒPThe GNU Free Documentation License, Version 1.2
(dual licensed under the GPL v2)”…””}”(hj?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhj*  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hàh³hÊh´KhhÝh²hubhá)”}”(hhh]”(hæ)”}”(hŒOriginal Reviewers”h]”hŒOriginal Reviewers”…””}”(hj\  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1håhjY  h³hÊh´K ubhö)”}”(hŒMElias Oltmanns, Randy Dunlap, Andrew Morton,
John Kacur, and David Teigland.
”h]”hÌ)”}”(hŒLElias Oltmanns, Randy Dunlap, Andrew Morton,
John Kacur, and David Teigland.”h]”hŒLElias Oltmanns, Randy Dunlap, Andrew Morton,
John Kacur, and David Teigland.”…””}”(hjn  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K
hjj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhjY  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hàh³hÊh´K
hhÝh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÛhh·h²hh³hÊh´KubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒWritten for: 2.6.28-rc2”h]”hÌ)”}”(hj—  h]”hŒWritten for: 2.6.28-rc2”…””}”(hj™  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj•  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  h²hh³hÊh´Nubj”  )”}”(hŒUpdated for: 3.10”h]”hÌ)”}”(hj®  h]”hŒUpdated for: 3.10”…””}”(hj°  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj¬  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  h²hh³hÊh´Nubj”  )”}”(hŒ=Updated for: 4.13 - Copyright 2017 VMware Inc. Steven Rostedt”h]”hÌ)”}”(hjÅ  h]”hŒ=Updated for: 4.13 - Copyright 2017 VMware Inc. Steven Rostedt”…””}”(hjÇ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KhjÃ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  h²hh³hÊh´Nubj”  )”}”(hŒ>Converted to rst format - Changbin Du <changbin.du@intel.com>
”h]”hÌ)”}”(hŒ=Converted to rst format - Changbin Du <changbin.du@intel.com>”h]”(hŒ'Converted to rst format - Changbin Du <”…””}”(hjÞ  h²hh³Nh´Nubj  )”}”(hŒchangbin.du@intel.com”h]”hŒchangbin.du@intel.com”…””}”(hjæ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:changbin.du@intel.com”uh1j  hjÞ  ubhŒ>”…””}”(hjÞ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KhjÚ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jŽ  h³hÊh´Khh·h²hubh¶)”}”(hhh]”(h»)”}”(hŒIntroduction”h]”hŒIntroduction”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj  h²hh³hÊh´KubhÌ)”}”(hŒóFtrace is an internal tracer designed to help out developers and
designers of systems to find what is going on inside the kernel.
It can be used for debugging or analyzing latencies and
performance issues that take place outside of user-space.”h]”hŒóFtrace is an internal tracer designed to help out developers and
designers of systems to find what is going on inside the kernel.
It can be used for debugging or analyzing latencies and
performance issues that take place outside of user-space.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj  h²hubhÌ)”}”(hX4  Although ftrace is typically considered the function tracer, it
is really a framework of several assorted tracing utilities.
There's latency tracing to examine what occurs between interrupts
disabled and enabled, as well as for preemption and from a time
a task is woken to the task is actually scheduled in.”h]”hX6  Although ftrace is typically considered the function tracer, it
is really a framework of several assorted tracing utilities.
Thereâ€™s latency tracing to examine what occurs between interrupts
disabled and enabled, as well as for preemption and from a time
a task is woken to the task is actually scheduled in.”…””}”(hj-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj  h²hubhÌ)”}”(hŒÝOne of the most common uses of ftrace is the event tracing.
Throughout the kernel are hundreds of static event points that
can be enabled via the tracefs file system to see what is
going on in certain parts of the kernel.”h]”hŒÝOne of the most common uses of ftrace is the event tracing.
Throughout the kernel are hundreds of static event points that
can be enabled via the tracefs file system to see what is
going on in certain parts of the kernel.”…””}”(hj;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hj  h²hubhÌ)”}”(hŒ$See events.rst for more information.”h]”hŒ$See events.rst for more information.”…””}”(hjI  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K%hj  h²hubeh}”(h]”Œintroduction”ah ]”h"]”Œintroduction”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒImplementation Details”h]”hŒImplementation Details”…””}”(hjb  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj_  h²hh³hÊh´K)ubhÌ)”}”(hŒPSee Documentation/trace/ftrace-design.rst for details for arch porters and such.”h]”hŒPSee Documentation/trace/ftrace-design.rst for details for arch porters and such.”…””}”(hjp  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K+hj_  h²hubeh}”(h]”Œimplementation-details”ah ]”h"]”Œimplementation details”ah$]”h&]”uh1hµhh·h²hh³hÊh´K)ubh¶)”}”(hhh]”(h»)”}”(hŒThe File System”h]”hŒThe File System”…””}”(hj‰  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj†  h²hh³hÊh´K/ubhÌ)”}”(hŒeFtrace uses the tracefs file system to hold the control files as
well as the files to display output.”h]”hŒeFtrace uses the tracefs file system to hold the control files as
well as the files to display output.”…””}”(hj—  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K1hj†  h²hubhÌ)”}”(hŒÈWhen tracefs is configured into the kernel (which selecting any ftrace
option will do) the directory /sys/kernel/tracing will be created. To mount
this directory, you can add to your /etc/fstab file::”h]”hŒÇWhen tracefs is configured into the kernel (which selecting any ftrace
option will do) the directory /sys/kernel/tracing will be created. To mount
this directory, you can add to your /etc/fstab file:”…””}”(hj¥  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K4hj†  h²hubhŒliteral_block”“”)”}”(hŒItracefs       /sys/kernel/tracing       tracefs defaults        0       0”h]”hŒItracefs       /sys/kernel/tracing       tracefs defaults        0       0”…””}”hjµ  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j³  h³hÊh´K8hj†  h²hubhÌ)”}”(hŒ&Or you can mount it at run time with::”h]”hŒ%Or you can mount it at run time with:”…””}”(hjÅ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K:hj†  h²hubj´  )”}”(hŒ*mount -t tracefs nodev /sys/kernel/tracing”h]”hŒ*mount -t tracefs nodev /sys/kernel/tracing”…””}”hjÓ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´K<hj†  h²hubhÌ)”}”(hŒMFor quicker access to that directory you may want to make a soft link to
it::”h]”hŒLFor quicker access to that directory you may want to make a soft link to
it:”…””}”(hjá  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K>hj†  h²hubj´  )”}”(hŒ"ln -s /sys/kernel/tracing /tracing”h]”hŒ"ln -s /sys/kernel/tracing /tracing”…””}”hjï  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´KAhj†  h²hubhŒ	attention”“”)”}”(hX  Before 4.1, all ftrace tracing control files were within the debugfs
file system, which is typically located at /sys/kernel/debug/tracing.
For backward compatibility, when mounting the debugfs file system,
the tracefs file system will be automatically mounted at:

/sys/kernel/debug/tracing

All files located in the tracefs file system will be located in that
debugfs file system directory as well.”h]”(hÌ)”}”(hX  Before 4.1, all ftrace tracing control files were within the debugfs
file system, which is typically located at /sys/kernel/debug/tracing.
For backward compatibility, when mounting the debugfs file system,
the tracefs file system will be automatically mounted at:”h]”hX  Before 4.1, all ftrace tracing control files were within the debugfs
file system, which is typically located at /sys/kernel/debug/tracing.
For backward compatibility, when mounting the debugfs file system,
the tracefs file system will be automatically mounted at:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KEhjÿ  ubhÌ)”}”(hŒ/sys/kernel/debug/tracing”h]”hŒ/sys/kernel/debug/tracing”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KJhjÿ  ubhÌ)”}”(hŒkAll files located in the tracefs file system will be located in that
debugfs file system directory as well.”h]”hŒkAll files located in the tracefs file system will be located in that
debugfs file system directory as well.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KLhjÿ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj†  h²hh³hÊh´Nubjþ  )”}”(hX9  Any selected ftrace option will also create the tracefs file system.
The rest of the document will assume that you are in the ftrace directory
(cd /sys/kernel/tracing) and will only concentrate on the files within that
directory and not distract from the content with the extended
"/sys/kernel/tracing" path name.”h]”hÌ)”}”(hX9  Any selected ftrace option will also create the tracefs file system.
The rest of the document will assume that you are in the ftrace directory
(cd /sys/kernel/tracing) and will only concentrate on the files within that
directory and not distract from the content with the extended
"/sys/kernel/tracing" path name.”h]”hX=  Any selected ftrace option will also create the tracefs file system.
The rest of the document will assume that you are in the ftrace directory
(cd /sys/kernel/tracing) and will only concentrate on the files within that
directory and not distract from the content with the extended
â€œ/sys/kernel/tracingâ€ path name.”…””}”(hj7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KQhj3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj†  h²hh³hÊh´NubhÌ)”}”(hŒFThat's it! (assuming that you have ftrace configured into your kernel)”h]”hŒHThatâ€™s it! (assuming that you have ftrace configured into your kernel)”…””}”(hjK  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KWhj†  h²hubhÌ)”}”(hŒAfter mounting tracefs you will have access to the control and output files
of ftrace. Here is a list of some of the key files:”h]”hŒAfter mounting tracefs you will have access to the control and output files
of ftrace. Here is a list of some of the key files:”…””}”(hjY  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KYhj†  h²hubhŒblock_quote”“”)”}”(hXco  Note: all time values are in microseconds.

 current_tracer:

       This is used to set or display the current tracer
       that is configured. Changing the current tracer clears
       the ring buffer content as well as the "snapshot" buffer.

 available_tracers:

       This holds the different types of tracers that
       have been compiled into the kernel. The
       tracers listed here can be configured by
       echoing their name into current_tracer.

 tracing_on:

       This sets or displays whether writing to the trace
       ring buffer is enabled. Echo 0 into this file to disable
       the tracer or 1 to enable it. Note, this only disables
       writing to the ring buffer, the tracing overhead may
       still be occurring.

       The kernel function tracing_off() can be used within the
       kernel to disable writing to the ring buffer, which will
       set this file to "0". User space can re-enable tracing by
       echoing "1" into the file.

       Note, the function and event trigger "traceoff" will also
       set this file to zero and stop tracing. Which can also
       be re-enabled by user space using this file.

 trace:

       This file holds the output of the trace in a human
       readable format (described below). Opening this file for
       writing with the O_TRUNC flag clears the ring buffer content.
       Note, this file is not a consumer. If tracing is off
       (no tracer running, or tracing_on is zero), it will produce
       the same output each time it is read. When tracing is on,
       it may produce inconsistent results as it tries to read
       the entire buffer without consuming it.

 trace_pipe:

       The output is the same as the "trace" file but this
       file is meant to be streamed with live tracing.
       Reads from this file will block until new data is
       retrieved.  Unlike the "trace" file, this file is a
       consumer. This means reading from this file causes
       sequential reads to display more current data. Once
       data is read from this file, it is consumed, and
       will not be read again with a sequential read. The
       "trace" file is static, and if the tracer is not
       adding more data, it will display the same
       information every time it is read.

 trace_options:

       This file lets the user control the amount of data
       that is displayed in one of the above output
       files. Options also exist to modify how a tracer
       or events work (stack traces, timestamps, etc).

 options:

       This is a directory that has a file for every available
       trace option (also in trace_options). Options may also be set
       or cleared by writing a "1" or "0" respectively into the
       corresponding file with the option name.

 tracing_max_latency:

       Some of the tracers record the max latency.
       For example, the maximum time that interrupts are disabled.
       The maximum time is saved in this file. The max trace will also be
       stored, and displayed by "trace". A new max trace will only be
       recorded if the latency is greater than the value in this file
       (in microseconds).

       By echoing in a time into this file, no latency will be recorded
       unless it is greater than the time in this file.

 tracing_thresh:

       Some latency tracers will record a trace whenever the
       latency is greater than the number in this file.
       Only active when the file contains a number greater than 0.
       (in microseconds)

 buffer_percent:

       This is the watermark for how much the ring buffer needs to be filled
       before a waiter is woken up. That is, if an application calls a
       blocking read syscall on one of the per_cpu trace_pipe_raw files, it
       will block until the given amount of data specified by buffer_percent
       is in the ring buffer before it wakes the reader up. This also
       controls how the splice system calls are blocked on this file::

         0   - means to wake up as soon as there is any data in the ring buffer.
         50  - means to wake up when roughly half of the ring buffer sub-buffers
               are full.
         100 - means to block until the ring buffer is totally full and is
               about to start overwriting the older data.

 buffer_size_kb:

       This sets or displays the number of kilobytes each CPU
       buffer holds. By default, the trace buffers are the same size
       for each CPU. The displayed number is the size of the
       CPU buffer and not total size of all buffers. The
       trace buffers are allocated in pages (blocks of memory
       that the kernel uses for allocation, usually 4 KB in size).
       A few extra pages may be allocated to accommodate buffer management
       meta-data. If the last page allocated has room for more bytes
       than requested, the rest of the page will be used,
       making the actual allocation bigger than requested or shown.
       ( Note, the size may not be a multiple of the page size
       due to buffer management meta-data. )

       Buffer sizes for individual CPUs may vary
       (see "per_cpu/cpu0/buffer_size_kb" below), and if they do
       this file will show "X".

 buffer_total_size_kb:

       This displays the total combined size of all the trace buffers.

 buffer_subbuf_size_kb:

       This sets or displays the sub buffer size. The ring buffer is broken up
       into several same size "sub buffers". An event can not be bigger than
       the size of the sub buffer. Normally, the sub buffer is the size of the
       architecture's page (4K on x86). The sub buffer also contains meta data
       at the start which also limits the size of an event.  That means when
       the sub buffer is a page size, no event can be larger than the page
       size minus the sub buffer meta data.

       Note, the buffer_subbuf_size_kb is a way for the user to specify the
       minimum size of the subbuffer. The kernel may make it bigger due to the
       implementation details, or simply fail the operation if the kernel can
       not handle the request.

       Changing the sub buffer size allows for events to be larger than the
       page size.

       Note: When changing the sub-buffer size, tracing is stopped and any
       data in the ring buffer and the snapshot buffer will be discarded.

 free_buffer:

       If a process is performing tracing, and the ring buffer should be
       shrunk "freed" when the process is finished, even if it were to be
       killed by a signal, this file can be used for that purpose. On close
       of this file, the ring buffer will be resized to its minimum size.
       Having a process that is tracing also open this file, when the process
       exits its file descriptor for this file will be closed, and in doing so,
       the ring buffer will be "freed".

       It may also stop tracing if disable_on_free option is set.

 tracing_cpumask:

       This is a mask that lets the user only trace on specified CPUs.
       The format is a hex string representing the CPUs.

 set_ftrace_filter:

       When dynamic ftrace is configured in (see the
       section below "dynamic ftrace"), the code is dynamically
       modified (code text rewrite) to disable calling of the
       function profiler (mcount). This lets tracing be configured
       in with practically no overhead in performance.  This also
       has a side effect of enabling or disabling specific functions
       to be traced. Echoing names of functions into this file
       will limit the trace to only those functions.
       This influences the tracers "function" and "function_graph"
       and thus also function profiling (see "function_profile_enabled").

       The functions listed in "available_filter_functions" are what
       can be written into this file.

       This interface also allows for commands to be used. See the
       "Filter commands" section for more details.

       As a speed up, since processing strings can be quite expensive
       and requires a check of all functions registered to tracing, instead
       an index can be written into this file. A number (starting with "1")
       written will instead select the same corresponding at the line position
       of the "available_filter_functions" file.

 set_ftrace_notrace:

       This has an effect opposite to that of
       set_ftrace_filter. Any function that is added here will not
       be traced. If a function exists in both set_ftrace_filter
       and set_ftrace_notrace, the function will _not_ be traced.

 set_ftrace_pid:

       Have the function tracer only trace the threads whose PID are
       listed in this file.

       If the "function-fork" option is set, then when a task whose
       PID is listed in this file forks, the child's PID will
       automatically be added to this file, and the child will be
       traced by the function tracer as well. This option will also
       cause PIDs of tasks that exit to be removed from the file.

 set_ftrace_notrace_pid:

       Have the function tracer ignore threads whose PID are listed in
       this file.

       If the "function-fork" option is set, then when a task whose
       PID is listed in this file forks, the child's PID will
       automatically be added to this file, and the child will not be
       traced by the function tracer as well. This option will also
       cause PIDs of tasks that exit to be removed from the file.

       If a PID is in both this file and "set_ftrace_pid", then this
       file takes precedence, and the thread will not be traced.

 set_event_pid:

       Have the events only trace a task with a PID listed in this file.
       Note, sched_switch and sched_wake_up will also trace events
       listed in this file.

       To have the PIDs of children of tasks with their PID in this file
       added on fork, enable the "event-fork" option. That option will also
       cause the PIDs of tasks to be removed from this file when the task
       exits.

 set_event_notrace_pid:

       Have the events not trace a task with a PID listed in this file.
       Note, sched_switch and sched_wakeup will trace threads not listed
       in this file, even if a thread's PID is in the file if the
       sched_switch or sched_wakeup events also trace a thread that should
       be traced.

       To have the PIDs of children of tasks with their PID in this file
       added on fork, enable the "event-fork" option. That option will also
       cause the PIDs of tasks to be removed from this file when the task
       exits.

 set_graph_function:

       Functions listed in this file will cause the function graph
       tracer to only trace these functions and the functions that
       they call. (See the section "dynamic ftrace" for more details).
       Note, set_ftrace_filter and set_ftrace_notrace still affects
       what functions are being traced.

 set_graph_notrace:

       Similar to set_graph_function, but will disable function graph
       tracing when the function is hit until it exits the function.
       This makes it possible to ignore tracing functions that are called
       by a specific function.

 available_filter_functions:

       This lists the functions that ftrace has processed and can trace.
       These are the function names that you can pass to
       "set_ftrace_filter", "set_ftrace_notrace",
       "set_graph_function", or "set_graph_notrace".
       (See the section "dynamic ftrace" below for more details.)

 available_filter_functions_addrs:

       Similar to available_filter_functions, but with address displayed
       for each function. The displayed address is the patch-site address
       and can differ from /proc/kallsyms address.

 syscall_user_buf_size:

       Some system call trace events will record the data from a user
       space address that one of the parameters point to. The amount of
       data per event is limited. This file holds the max number of bytes
       that will be recorded into the ring buffer to hold this data.
       The max value is currently 165.

 dyn_ftrace_total_info:

       This file is for debugging purposes. The number of functions that
       have been converted to nops and are available to be traced.

 enabled_functions:

       This file is more for debugging ftrace, but can also be useful
       in seeing if any function has a callback attached to it.
       Not only does the trace infrastructure use ftrace function
       trace utility, but other subsystems might too. This file
       displays all functions that have a callback attached to them
       as well as the number of callbacks that have been attached.
       Note, a callback may also call multiple functions which will
       not be listed in this count.

       If the callback registered to be traced by a function with
       the "save regs" attribute (thus even more overhead), an 'R'
       will be displayed on the same line as the function that
       is returning registers.

       If the callback registered to be traced by a function with
       the "ip modify" attribute (thus the regs->ip can be changed),
       an 'I' will be displayed on the same line as the function that
       can be overridden.

       If a non-ftrace trampoline is attached (BPF) a 'D' will be displayed.
       Note, normal ftrace trampolines can also be attached, but only one
       "direct" trampoline can be attached to a given function at a time.

       Some architectures can not call direct trampolines, but instead have
       the ftrace ops function located above the function entry point. In
       such cases an 'O' will be displayed.

       If a function had either the "ip modify" or a "direct" call attached to
       it in the past, a 'M' will be shown. This flag is never cleared. It is
       used to know if a function was ever modified by the ftrace infrastructure,
       and can be used for debugging.

       If the architecture supports it, it will also show what callback
       is being directly called by the function. If the count is greater
       than 1 it most likely will be ftrace_ops_list_func().

       If the callback of a function jumps to a trampoline that is
       specific to the callback and which is not the standard trampoline,
       its address will be printed as well as the function that the
       trampoline calls.

 touched_functions:

       This file contains all the functions that ever had a function callback
       to it via the ftrace infrastructure. It has the same format as
       enabled_functions but shows all functions that have ever been
       traced.

       To see any function that has every been modified by "ip modify" or a
       direct trampoline, one can perform the following command:

       grep ' M ' /sys/kernel/tracing/touched_functions

 function_profile_enabled:

       When set it will enable all functions with either the function
       tracer, or if configured, the function graph tracer. It will
       keep a histogram of the number of functions that were called
       and if the function graph tracer was configured, it will also keep
       track of the time spent in those functions. The histogram
       content can be displayed in the files:

       trace_stat/function<cpu> ( function0, function1, etc).

 trace_stat:

       A directory that holds different tracing stats.

 kprobe_events:

       Enable dynamic trace points. See kprobetrace.rst.

 kprobe_profile:

       Dynamic trace points stats. See kprobetrace.rst.

 max_graph_depth:

       Used with the function graph tracer. This is the max depth
       it will trace into a function. Setting this to a value of
       one will show only the first kernel function that is called
       from user space.

 printk_formats:

       This is for tools that read the raw format files. If an event in
       the ring buffer references a string, only a pointer to the string
       is recorded into the buffer and not the string itself. This prevents
       tools from knowing what that string was. This file displays the string
       and address for the string allowing tools to map the pointers to what
       the strings were.

 saved_cmdlines:

       Only the pid of the task is recorded in a trace event unless
       the event specifically saves the task comm as well. Ftrace
       makes a cache of pid mappings to comms to try to display
       comms for events. If a pid for a comm is not listed, then
       "<...>" is displayed in the output.

       If the option "record-cmd" is set to "0", then comms of tasks
       will not be saved during recording. By default, it is enabled.

 saved_cmdlines_size:

       By default, 128 comms are saved (see "saved_cmdlines" above). To
       increase or decrease the amount of comms that are cached, echo
       the number of comms to cache into this file.

 saved_tgids:

       If the option "record-tgid" is set, on each scheduling context switch
       the Task Group ID of a task is saved in a table mapping the PID of
       the thread to its TGID. By default, the "record-tgid" option is
       disabled.

 snapshot:

       This displays the "snapshot" buffer and also lets the user
       take a snapshot of the current running trace.
       See the "Snapshot" section below for more details.

 stack_max_size:

       When the stack tracer is activated, this will display the
       maximum stack size it has encountered.
       See the "Stack Trace" section below.

 stack_trace:

       This displays the stack back trace of the largest stack
       that was encountered when the stack tracer is activated.
       See the "Stack Trace" section below.

 stack_trace_filter:

       This is similar to "set_ftrace_filter" but it limits what
       functions the stack tracer will check.

 trace_clock:

       Whenever an event is recorded into the ring buffer, a
       "timestamp" is added. This stamp comes from a specified
       clock. By default, ftrace uses the "local" clock. This
       clock is very fast and strictly per CPU, but on some
       systems it may not be monotonic with respect to other
       CPUs. In other words, the local clocks may not be in sync
       with local clocks on other CPUs.

       Usual clocks for tracing::

         # cat trace_clock
         [local] global counter x86-tsc

       The clock with the square brackets around it is the one in effect.

       local:
               Default clock, but may not be in sync across CPUs

       global:
               This clock is in sync with all CPUs but may
               be a bit slower than the local clock.

       counter:
               This is not a clock at all, but literally an atomic
               counter. It counts up one by one, but is in sync
               with all CPUs. This is useful when you need to
               know exactly the order events occurred with respect to
               each other on different CPUs.

       uptime:
               This uses the jiffies counter and the time stamp
               is relative to the time since boot up.

       perf:
               This makes ftrace use the same clock that perf uses.
               Eventually perf will be able to read ftrace buffers
               and this will help out in interleaving the data.

       x86-tsc:
               Architectures may define their own clocks. For
               example, x86 uses its own TSC cycle clock here.

       ppc-tb:
               This uses the powerpc timebase register value.
               This is in sync across CPUs and can also be used
               to correlate events across hypervisor/guest if
               tb_offset is known.

       s390-tod:
               This uses the s390 TOD clock value. This clock is usually in
               sync across virtual machines and STP-enabled machines.

       mono:
               This uses the fast monotonic clock (CLOCK_MONOTONIC)
               which is monotonic and is subject to NTP rate adjustments.

       mono_raw:
               This is the raw monotonic clock (CLOCK_MONOTONIC_RAW)
               which is monotonic but is not subject to any rate adjustments
               and ticks at the same rate as the hardware clocksource.

       boot:
               This is the boot clock (CLOCK_BOOTTIME) and is based on the
               fast monotonic clock, but also accounts for time spent in
               suspend. Since the clock access is designed for use in
               tracing in the suspend path, some side effects are possible
               if clock is accessed after the suspend time is accounted before
               the fast mono clock is updated. In this case, the clock update
               appears to happen slightly sooner than it normally would have.
               Also on 32-bit systems, it's possible that the 64-bit boot offset
               sees a partial update. These effects are rare and post
               processing should be able to handle them. See comments in the
               ktime_get_boot_fast_ns() function for more information.

       tai:
               This is the tai clock (CLOCK_TAI) and is derived from the wall-
               clock time. However, this clock does not experience
               discontinuities and backwards jumps caused by NTP inserting leap
               seconds. Since the clock access is designed for use in tracing,
               side effects are possible. The clock access may yield wrong
               readouts in case the internal TAI offset is updated e.g., caused
               by setting the system time or using adjtimex() with an offset.
               These effects are rare and post processing should be able to
               handle them. See comments in the ktime_get_tai_fast_ns()
               function for more information.

       To set a clock, simply echo the clock name into this file::

         # echo global > trace_clock

       Setting a clock clears the ring buffer content as well as the
       "snapshot" buffer.

 trace_marker:

       This is a very useful file for synchronizing user space
       with events happening in the kernel. Writing strings into
       this file will be written into the ftrace buffer.

       It is useful in applications to open this file at the start
       of the application and just reference the file descriptor
       for the file::

               void trace_write(const char *fmt, ...)
               {
                       va_list ap;
                       char buf[256];
                       int n;

                       if (trace_fd < 0)
                               return;

                       va_start(ap, fmt);
                       n = vsnprintf(buf, 256, fmt, ap);
                       va_end(ap);

                       write(trace_fd, buf, n);
               }

       start::

               trace_fd = open("trace_marker", O_WRONLY);

       Note: Writing into the trace_marker file can also initiate triggers
             that are written into /sys/kernel/tracing/events/ftrace/print/trigger
             See "Event triggers" in Documentation/trace/events.rst and an
             example in Documentation/trace/histogram.rst (Section 3.)

 trace_marker_raw:

       This is similar to trace_marker above, but is meant for binary data
       to be written to it, where a tool can be used to parse the data
       from trace_pipe_raw.

 uprobe_events:

       Add dynamic tracepoints in programs.
       See uprobetracer.rst

 uprobe_profile:

       Uprobe statistics. See uprobetrace.txt

 instances:

       This is a way to make multiple trace buffers where different
       events can be recorded in different buffers.
       See "Instances" section below.

 events:

       This is the trace event directory. It holds event tracepoints
       (also known as static tracepoints) that have been compiled
       into the kernel. It shows what event tracepoints exist
       and how they are grouped by system. There are "enable"
       files at various levels that can enable the tracepoints
       when a "1" is written to them.

       See events.rst for more information.

 set_event:

       By echoing in the event into this file, will enable that event.

       See events.rst for more information.

 show_event_filters:

       A list of events that have filters. This shows the
       system/event pair along with the filter that is attached to
       the event.

       See events.rst for more information.

 show_event_triggers:

       A list of events that have triggers. This shows the
       system/event pair along with the trigger that is attached to
       the event.

       See events.rst for more information.

 available_events:

       A list of events that can be enabled in tracing.

       See events.rst for more information.

 timestamp_mode:

       Certain tracers may change the timestamp mode used when
       logging trace events into the event buffer.  Events with
       different modes can coexist within a buffer but the mode in
       effect when an event is logged determines which timestamp mode
       is used for that event.  The default timestamp mode is
       'delta'.

       Usual timestamp modes for tracing:

         # cat timestamp_mode
         [delta] absolute

         The timestamp mode with the square brackets around it is the
         one in effect.

         delta: Default timestamp mode - timestamp is a delta against
                a per-buffer timestamp.

         absolute: The timestamp is a full timestamp, not a delta
                against some other value.  As such it takes up more
                space and is less efficient.

 hwlat_detector:

       Directory for the Hardware Latency Detector.
       See "Hardware Latency Detector" section below.

 per_cpu:

       This is a directory that contains the trace per_cpu information.

 per_cpu/cpu0/buffer_size_kb:

       The ftrace buffer is defined per_cpu. That is, there's a separate
       buffer for each CPU to allow writes to be done atomically,
       and free from cache bouncing. These buffers may have different
       size buffers. This file is similar to the buffer_size_kb
       file, but it only displays or sets the buffer size for the
       specific CPU. (here cpu0).

 per_cpu/cpu0/trace:

       This is similar to the "trace" file, but it will only display
       the data specific for the CPU. If written to, it only clears
       the specific CPU buffer.

 per_cpu/cpu0/trace_pipe

       This is similar to the "trace_pipe" file, and is a consuming
       read, but it will only display (and consume) the data specific
       for the CPU.

 per_cpu/cpu0/trace_pipe_raw

       For tools that can parse the ftrace ring buffer binary format,
       the trace_pipe_raw file can be used to extract the data
       from the ring buffer directly. With the use of the splice()
       system call, the buffer data can be quickly transferred to
       a file or to the network where a server is collecting the
       data.

       Like trace_pipe, this is a consuming reader, where multiple
       reads will always produce different data.

 per_cpu/cpu0/snapshot:

       This is similar to the main "snapshot" file, but will only
       snapshot the current CPU (if supported). It only displays
       the content of the snapshot for a given CPU, and if
       written to, only clears this CPU buffer.

 per_cpu/cpu0/snapshot_raw:

       Similar to the trace_pipe_raw, but will read the binary format
       from the snapshot buffer for the given CPU.

 per_cpu/cpu0/stats:

       This displays certain stats about the ring buffer:

       entries:
               The number of events that are still in the buffer.

       overrun:
               The number of lost events due to overwriting when
               the buffer was full.

       commit overrun:
               Should always be zero.
               This gets set if so many events happened within a nested
               event (ring buffer is re-entrant), that it fills the
               buffer and starts dropping events.

       bytes:
               Bytes actually read (not overwritten).

       oldest event ts:
               The oldest timestamp in the buffer

       now ts:
               The current timestamp

       dropped events:
               Events lost due to overwrite option being off.

       read events:
               The number of events read.
”h]”(hÌ)”}”(hŒ*Note: all time values are in microseconds.”h]”hŒ*Note: all time values are in microseconds.”…””}”(hjm  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K]hji  ubjh  )”}”(hX&m  current_tracer:

      This is used to set or display the current tracer
      that is configured. Changing the current tracer clears
      the ring buffer content as well as the "snapshot" buffer.

available_tracers:

      This holds the different types of tracers that
      have been compiled into the kernel. The
      tracers listed here can be configured by
      echoing their name into current_tracer.

tracing_on:

      This sets or displays whether writing to the trace
      ring buffer is enabled. Echo 0 into this file to disable
      the tracer or 1 to enable it. Note, this only disables
      writing to the ring buffer, the tracing overhead may
      still be occurring.

      The kernel function tracing_off() can be used within the
      kernel to disable writing to the ring buffer, which will
      set this file to "0". User space can re-enable tracing by
      echoing "1" into the file.

      Note, the function and event trigger "traceoff" will also
      set this file to zero and stop tracing. Which can also
      be re-enabled by user space using this file.

trace:

      This file holds the output of the trace in a human
      readable format (described below). Opening this file for
      writing with the O_TRUNC flag clears the ring buffer content.
      Note, this file is not a consumer. If tracing is off
      (no tracer running, or tracing_on is zero), it will produce
      the same output each time it is read. When tracing is on,
      it may produce inconsistent results as it tries to read
      the entire buffer without consuming it.

trace_pipe:

      The output is the same as the "trace" file but this
      file is meant to be streamed with live tracing.
      Reads from this file will block until new data is
      retrieved.  Unlike the "trace" file, this file is a
      consumer. This means reading from this file causes
      sequential reads to display more current data. Once
      data is read from this file, it is consumed, and
      will not be read again with a sequential read. The
      "trace" file is static, and if the tracer is not
      adding more data, it will display the same
      information every time it is read.

trace_options:

      This file lets the user control the amount of data
      that is displayed in one of the above output
      files. Options also exist to modify how a tracer
      or events work (stack traces, timestamps, etc).

options:

      This is a directory that has a file for every available
      trace option (also in trace_options). Options may also be set
      or cleared by writing a "1" or "0" respectively into the
      corresponding file with the option name.

tracing_max_latency:

      Some of the tracers record the max latency.
      For example, the maximum time that interrupts are disabled.
      The maximum time is saved in this file. The max trace will also be
      stored, and displayed by "trace". A new max trace will only be
      recorded if the latency is greater than the value in this file
      (in microseconds).

      By echoing in a time into this file, no latency will be recorded
      unless it is greater than the time in this file.

tracing_thresh:

      Some latency tracers will record a trace whenever the
      latency is greater than the number in this file.
      Only active when the file contains a number greater than 0.
      (in microseconds)

buffer_percent:

      This is the watermark for how much the ring buffer needs to be filled
      before a waiter is woken up. That is, if an application calls a
      blocking read syscall on one of the per_cpu trace_pipe_raw files, it
      will block until the given amount of data specified by buffer_percent
      is in the ring buffer before it wakes the reader up. This also
      controls how the splice system calls are blocked on this file::

        0   - means to wake up as soon as there is any data in the ring buffer.
        50  - means to wake up when roughly half of the ring buffer sub-buffers
              are full.
        100 - means to block until the ring buffer is totally full and is
              about to start overwriting the older data.

buffer_size_kb:

      This sets or displays the number of kilobytes each CPU
      buffer holds. By default, the trace buffers are the same size
      for each CPU. The displayed number is the size of the
      CPU buffer and not total size of all buffers. The
      trace buffers are allocated in pages (blocks of memory
      that the kernel uses for allocation, usually 4 KB in size).
      A few extra pages may be allocated to accommodate buffer management
      meta-data. If the last page allocated has room for more bytes
      than requested, the rest of the page will be used,
      making the actual allocation bigger than requested or shown.
      ( Note, the size may not be a multiple of the page size
      due to buffer management meta-data. )

      Buffer sizes for individual CPUs may vary
      (see "per_cpu/cpu0/buffer_size_kb" below), and if they do
      this file will show "X".

buffer_total_size_kb:

      This displays the total combined size of all the trace buffers.

buffer_subbuf_size_kb:

      This sets or displays the sub buffer size. The ring buffer is broken up
      into several same size "sub buffers". An event can not be bigger than
      the size of the sub buffer. Normally, the sub buffer is the size of the
      architecture's page (4K on x86). The sub buffer also contains meta data
      at the start which also limits the size of an event.  That means when
      the sub buffer is a page size, no event can be larger than the page
      size minus the sub buffer meta data.

      Note, the buffer_subbuf_size_kb is a way for the user to specify the
      minimum size of the subbuffer. The kernel may make it bigger due to the
      implementation details, or simply fail the operation if the kernel can
      not handle the request.

      Changing the sub buffer size allows for events to be larger than the
      page size.

      Note: When changing the sub-buffer size, tracing is stopped and any
      data in the ring buffer and the snapshot buffer will be discarded.

free_buffer:

      If a process is performing tracing, and the ring buffer should be
      shrunk "freed" when the process is finished, even if it were to be
      killed by a signal, this file can be used for that purpose. On close
      of this file, the ring buffer will be resized to its minimum size.
      Having a process that is tracing also open this file, when the process
      exits its file descriptor for this file will be closed, and in doing so,
      the ring buffer will be "freed".

      It may also stop tracing if disable_on_free option is set.

tracing_cpumask:

      This is a mask that lets the user only trace on specified CPUs.
      The format is a hex string representing the CPUs.

set_ftrace_filter:

      When dynamic ftrace is configured in (see the
      section below "dynamic ftrace"), the code is dynamically
      modified (code text rewrite) to disable calling of the
      function profiler (mcount). This lets tracing be configured
      in with practically no overhead in performance.  This also
      has a side effect of enabling or disabling specific functions
      to be traced. Echoing names of functions into this file
      will limit the trace to only those functions.
      This influences the tracers "function" and "function_graph"
      and thus also function profiling (see "function_profile_enabled").

      The functions listed in "available_filter_functions" are what
      can be written into this file.

      This interface also allows for commands to be used. See the
      "Filter commands" section for more details.

      As a speed up, since processing strings can be quite expensive
      and requires a check of all functions registered to tracing, instead
      an index can be written into this file. A number (starting with "1")
      written will instead select the same corresponding at the line position
      of the "available_filter_functions" file.

set_ftrace_notrace:

      This has an effect opposite to that of
      set_ftrace_filter. Any function that is added here will not
      be traced. If a function exists in both set_ftrace_filter
      and set_ftrace_notrace, the function will _not_ be traced.

set_ftrace_pid:

      Have the function tracer only trace the threads whose PID are
      listed in this file.

      If the "function-fork" option is set, then when a task whose
      PID is listed in this file forks, the child's PID will
      automatically be added to this file, and the child will be
      traced by the function tracer as well. This option will also
      cause PIDs of tasks that exit to be removed from the file.

set_ftrace_notrace_pid:

      Have the function tracer ignore threads whose PID are listed in
      this file.

      If the "function-fork" option is set, then when a task whose
      PID is listed in this file forks, the child's PID will
      automatically be added to this file, and the child will not be
      traced by the function tracer as well. This option will also
      cause PIDs of tasks that exit to be removed from the file.

      If a PID is in both this file and "set_ftrace_pid", then this
      file takes precedence, and the thread will not be traced.

set_event_pid:

      Have the events only trace a task with a PID listed in this file.
      Note, sched_switch and sched_wake_up will also trace events
      listed in this file.

      To have the PIDs of children of tasks with their PID in this file
      added on fork, enable the "event-fork" option. That option will also
      cause the PIDs of tasks to be removed from this file when the task
      exits.

set_event_notrace_pid:

      Have the events not trace a task with a PID listed in this file.
      Note, sched_switch and sched_wakeup will trace threads not listed
      in this file, even if a thread's PID is in the file if the
      sched_switch or sched_wakeup events also trace a thread that should
      be traced.

      To have the PIDs of children of tasks with their PID in this file
      added on fork, enable the "event-fork" option. That option will also
      cause the PIDs of tasks to be removed from this file when the task
      exits.

set_graph_function:

      Functions listed in this file will cause the function graph
      tracer to only trace these functions and the functions that
      they call. (See the section "dynamic ftrace" for more details).
      Note, set_ftrace_filter and set_ftrace_notrace still affects
      what functions are being traced.

set_graph_notrace:

      Similar to set_graph_function, but will disable function graph
      tracing when the function is hit until it exits the function.
      This makes it possible to ignore tracing functions that are called
      by a specific function.

available_filter_functions:

      This lists the functions that ftrace has processed and can trace.
      These are the function names that you can pass to
      "set_ftrace_filter", "set_ftrace_notrace",
      "set_graph_function", or "set_graph_notrace".
      (See the section "dynamic ftrace" below for more details.)

available_filter_functions_addrs:

      Similar to available_filter_functions, but with address displayed
      for each function. The displayed address is the patch-site address
      and can differ from /proc/kallsyms address.

syscall_user_buf_size:

      Some system call trace events will record the data from a user
      space address that one of the parameters point to. The amount of
      data per event is limited. This file holds the max number of bytes
      that will be recorded into the ring buffer to hold this data.
      The max value is currently 165.

dyn_ftrace_total_info:

      This file is for debugging purposes. The number of functions that
      have been converted to nops and are available to be traced.

enabled_functions:

      This file is more for debugging ftrace, but can also be useful
      in seeing if any function has a callback attached to it.
      Not only does the trace infrastructure use ftrace function
      trace utility, but other subsystems might too. This file
      displays all functions that have a callback attached to them
      as well as the number of callbacks that have been attached.
      Note, a callback may also call multiple functions which will
      not be listed in this count.

      If the callback registered to be traced by a function with
      the "save regs" attribute (thus even more overhead), an 'R'
      will be displayed on the same line as the function that
      is returning registers.

      If the callback registered to be traced by a function with
      the "ip modify" attribute (thus the regs->ip can be changed),
      an 'I' will be displayed on the same line as the function that
      can be overridden.

      If a non-ftrace trampoline is attached (BPF) a 'D' will be displayed.
      Note, normal ftrace trampolines can also be attached, but only one
      "direct" trampoline can be attached to a given function at a time.

      Some architectures can not call direct trampolines, but instead have
      the ftrace ops function located above the function entry point. In
      such cases an 'O' will be displayed.

      If a function had either the "ip modify" or a "direct" call attached to
      it in the past, a 'M' will be shown. This flag is never cleared. It is
      used to know if a function was ever modified by the ftrace infrastructure,
      and can be used for debugging.

      If the architecture supports it, it will also show what callback
      is being directly called by the function. If the count is greater
      than 1 it most likely will be ftrace_ops_list_func().

      If the callback of a function jumps to a trampoline that is
      specific to the callback and which is not the standard trampoline,
      its address will be printed as well as the function that the
      trampoline calls.

touched_functions:

      This file contains all the functions that ever had a function callback
      to it via the ftrace infrastructure. It has the same format as
      enabled_functions but shows all functions that have ever been
      traced.

      To see any function that has every been modified by "ip modify" or a
      direct trampoline, one can perform the following command:

      grep ' M ' /sys/kernel/tracing/touched_functions

function_profile_enabled:

      When set it will enable all functions with either the function
      tracer, or if configured, the function graph tracer. It will
      keep a histogram of the number of functions that were called
      and if the function graph tracer was configured, it will also keep
      track of the time spent in those functions. The histogram
      content can be displayed in the files:

      trace_stat/function<cpu> ( function0, function1, etc).

trace_stat:

      A directory that holds different tracing stats.

kprobe_events:

      Enable dynamic trace points. See kprobetrace.rst.

kprobe_profile:

      Dynamic trace points stats. See kprobetrace.rst.

max_graph_depth:

      Used with the function graph tracer. This is the max depth
      it will trace into a function. Setting this to a value of
      one will show only the first kernel function that is called
      from user space.

printk_formats:

      This is for tools that read the raw format files. If an event in
      the ring buffer references a string, only a pointer to the string
      is recorded into the buffer and not the string itself. This prevents
      tools from knowing what that string was. This file displays the string
      and address for the string allowing tools to map the pointers to what
      the strings were.

saved_cmdlines:

      Only the pid of the task is recorded in a trace event unless
      the event specifically saves the task comm as well. Ftrace
      makes a cache of pid mappings to comms to try to display
      comms for events. If a pid for a comm is not listed, then
      "<...>" is displayed in the output.

      If the option "record-cmd" is set to "0", then comms of tasks
      will not be saved during recording. By default, it is enabled.

saved_cmdlines_size:

      By default, 128 comms are saved (see "saved_cmdlines" above). To
      increase or decrease the amount of comms that are cached, echo
      the number of comms to cache into this file.

saved_tgids:

      If the option "record-tgid" is set, on each scheduling context switch
      the Task Group ID of a task is saved in a table mapping the PID of
      the thread to its TGID. By default, the "record-tgid" option is
      disabled.

snapshot:

      This displays the "snapshot" buffer and also lets the user
      take a snapshot of the current running trace.
      See the "Snapshot" section below for more details.

stack_max_size:

      When the stack tracer is activated, this will display the
      maximum stack size it has encountered.
      See the "Stack Trace" section below.

stack_trace:

      This displays the stack back trace of the largest stack
      that was encountered when the stack tracer is activated.
      See the "Stack Trace" section below.

stack_trace_filter:

      This is similar to "set_ftrace_filter" but it limits what
      functions the stack tracer will check.

trace_clock:

      Whenever an event is recorded into the ring buffer, a
      "timestamp" is added. This stamp comes from a specified
      clock. By default, ftrace uses the "local" clock. This
      clock is very fast and strictly per CPU, but on some
      systems it may not be monotonic with respect to other
      CPUs. In other words, the local clocks may not be in sync
      with local clocks on other CPUs.

      Usual clocks for tracing::

        # cat trace_clock
        [local] global counter x86-tsc

      The clock with the square brackets around it is the one in effect.

      local:
              Default clock, but may not be in sync across CPUs

      global:
              This clock is in sync with all CPUs but may
              be a bit slower than the local clock.

      counter:
              This is not a clock at all, but literally an atomic
              counter. It counts up one by one, but is in sync
              with all CPUs. This is useful when you need to
              know exactly the order events occurred with respect to
              each other on different CPUs.

      uptime:
              This uses the jiffies counter and the time stamp
              is relative to the time since boot up.

      perf:
              This makes ftrace use the same clock that perf uses.
              Eventually perf will be able to read ftrace buffers
              and this will help out in interleaving the data.

      x86-tsc:
              Architectures may define their own clocks. For
              example, x86 uses its own TSC cycle clock here.

      ppc-tb:
              This uses the powerpc timebase register value.
              This is in sync across CPUs and can also be used
              to correlate events across hypervisor/guest if
              tb_offset is known.

      s390-tod:
              This uses the s390 TOD clock value. This clock is usually in
              sync across virtual machines and STP-enabled machines.

      mono:
              This uses the fast monotonic clock (CLOCK_MONOTONIC)
              which is monotonic and is subject to NTP rate adjustments.

      mono_raw:
              This is the raw monotonic clock (CLOCK_MONOTONIC_RAW)
              which is monotonic but is not subject to any rate adjustments
              and ticks at the same rate as the hardware clocksource.

      boot:
              This is the boot clock (CLOCK_BOOTTIME) and is based on the
              fast monotonic clock, but also accounts for time spent in
              suspend. Since the clock access is designed for use in
              tracing in the suspend path, some side effects are possible
              if clock is accessed after the suspend time is accounted before
              the fast mono clock is updated. In this case, the clock update
              appears to happen slightly sooner than it normally would have.
              Also on 32-bit systems, it's possible that the 64-bit boot offset
              sees a partial update. These effects are rare and post
              processing should be able to handle them. See comments in the
              ktime_get_boot_fast_ns() function for more information.

      tai:
              This is the tai clock (CLOCK_TAI) and is derived from the wall-
              clock time. However, this clock does not experience
              discontinuities and backwards jumps caused by NTP inserting leap
              seconds. Since the clock access is designed for use in tracing,
              side effects are possible. The clock access may yield wrong
              readouts in case the internal TAI offset is updated e.g., caused
              by setting the system time or using adjtimex() with an offset.
              These effects are rare and post processing should be able to
              handle them. See comments in the ktime_get_tai_fast_ns()
              function for more information.

      To set a clock, simply echo the clock name into this file::

        # echo global > trace_clock

      Setting a clock clears the ring buffer content as well as the
      "snapshot" buffer.

trace_marker:

      This is a very useful file for synchronizing user space
      with events happening in the kernel. Writing strings into
      this file will be written into the ftrace buffer.

      It is useful in applications to open this file at the start
      of the application and just reference the file descriptor
      for the file::

              void trace_write(const char *fmt, ...)
              {
                      va_list ap;
                      char buf[256];
                      int n;

                      if (trace_fd < 0)
                              return;

                      va_start(ap, fmt);
                      n = vsnprintf(buf, 256, fmt, ap);
                      va_end(ap);

                      write(trace_fd, buf, n);
              }

      start::

              trace_fd = open("trace_marker", O_WRONLY);

      Note: Writing into the trace_marker file can also initiate triggers
            that are written into /sys/kernel/tracing/events/ftrace/print/trigger
            See "Event triggers" in Documentation/trace/events.rst and an
            example in Documentation/trace/histogram.rst (Section 3.)

trace_marker_raw:

      This is similar to trace_marker above, but is meant for binary data
      to be written to it, where a tool can be used to parse the data
      from trace_pipe_raw.

uprobe_events:

      Add dynamic tracepoints in programs.
      See uprobetracer.rst

uprobe_profile:

      Uprobe statistics. See uprobetrace.txt

instances:

      This is a way to make multiple trace buffers where different
      events can be recorded in different buffers.
      See "Instances" section below.

events:

      This is the trace event directory. It holds event tracepoints
      (also known as static tracepoints) that have been compiled
      into the kernel. It shows what event tracepoints exist
      and how they are grouped by system. There are "enable"
      files at various levels that can enable the tracepoints
      when a "1" is written to them.

      See events.rst for more information.

set_event:

      By echoing in the event into this file, will enable that event.

      See events.rst for more information.

show_event_filters:

      A list of events that have filters. This shows the
      system/event pair along with the filter that is attached to
      the event.

      See events.rst for more information.

show_event_triggers:

      A list of events that have triggers. This shows the
      system/event pair along with the trigger that is attached to
      the event.

      See events.rst for more information.

available_events:

      A list of events that can be enabled in tracing.

      See events.rst for more information.

timestamp_mode:

      Certain tracers may change the timestamp mode used when
      logging trace events into the event buffer.  Events with
      different modes can coexist within a buffer but the mode in
      effect when an event is logged determines which timestamp mode
      is used for that event.  The default timestamp mode is
      'delta'.

      Usual timestamp modes for tracing:

        # cat timestamp_mode
        [delta] absolute

        The timestamp mode with the square brackets around it is the
        one in effect.

        delta: Default timestamp mode - timestamp is a delta against
               a per-buffer timestamp.

        absolute: The timestamp is a full timestamp, not a delta
               against some other value.  As such it takes up more
               space and is less efficient.

hwlat_detector:

      Directory for the Hardware Latency Detector.
      See "Hardware Latency Detector" section below.

per_cpu:

      This is a directory that contains the trace per_cpu information.

per_cpu/cpu0/buffer_size_kb:

      The ftrace buffer is defined per_cpu. That is, there's a separate
      buffer for each CPU to allow writes to be done atomically,
      and free from cache bouncing. These buffers may have different
      size buffers. This file is similar to the buffer_size_kb
      file, but it only displays or sets the buffer size for the
      specific CPU. (here cpu0).

per_cpu/cpu0/trace:

      This is similar to the "trace" file, but it will only display
      the data specific for the CPU. If written to, it only clears
      the specific CPU buffer.

per_cpu/cpu0/trace_pipe

      This is similar to the "trace_pipe" file, and is a consuming
      read, but it will only display (and consume) the data specific
      for the CPU.

per_cpu/cpu0/trace_pipe_raw

      For tools that can parse the ftrace ring buffer binary format,
      the trace_pipe_raw file can be used to extract the data
      from the ring buffer directly. With the use of the splice()
      system call, the buffer data can be quickly transferred to
      a file or to the network where a server is collecting the
      data.

      Like trace_pipe, this is a consuming reader, where multiple
      reads will always produce different data.

per_cpu/cpu0/snapshot:

      This is similar to the main "snapshot" file, but will only
      snapshot the current CPU (if supported). It only displays
      the content of the snapshot for a given CPU, and if
      written to, only clears this CPU buffer.

per_cpu/cpu0/snapshot_raw:

      Similar to the trace_pipe_raw, but will read the binary format
      from the snapshot buffer for the given CPU.

per_cpu/cpu0/stats:

      This displays certain stats about the ring buffer:

      entries:
              The number of events that are still in the buffer.

      overrun:
              The number of lost events due to overwriting when
              the buffer was full.

      commit overrun:
              Should always be zero.
              This gets set if so many events happened within a nested
              event (ring buffer is re-entrant), that it fills the
              buffer and starts dropping events.

      bytes:
              Bytes actually read (not overwritten).

      oldest event ts:
              The oldest timestamp in the buffer

      now ts:
              The current timestamp

      dropped events:
              Events lost due to overwrite option being off.

      read events:
              The number of events read.
”•      h]”(hÌ)”}”(hŒcurrent_tracer:”h]”hŒcurrent_tracer:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K_hj{  ubjh  )”}”(hŒ£This is used to set or display the current tracer
that is configured. Changing the current tracer clears
the ring buffer content as well as the "snapshot" buffer.
”h]”hÌ)”}”(hŒ¢This is used to set or display the current tracer
that is configured. Changing the current tracer clears
the ring buffer content as well as the "snapshot" buffer.”h]”hŒ¦This is used to set or display the current tracer
that is configured. Changing the current tracer clears
the ring buffer content as well as the â€œsnapshotâ€ buffer.”…””}”(hj‘  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kahj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Kahj{  ubhÌ)”}”(hŒavailable_tracers:”h]”hŒavailable_tracers:”…””}”(hj¥  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kehj{  ubjh  )”}”(hŒ¨This holds the different types of tracers that
have been compiled into the kernel. The
tracers listed here can be configured by
echoing their name into current_tracer.
”h]”hÌ)”}”(hŒ§This holds the different types of tracers that
have been compiled into the kernel. The
tracers listed here can be configured by
echoing their name into current_tracer.”h]”hŒ§This holds the different types of tracers that
have been compiled into the kernel. The
tracers listed here can be configured by
echoing their name into current_tracer.”…””}”(hj·  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kghj³  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Kghj{  ubhÌ)”}”(hŒtracing_on:”h]”hŒtracing_on:”…””}”(hjË  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Klhj{  ubjh  )”}”(hXS  This sets or displays whether writing to the trace
ring buffer is enabled. Echo 0 into this file to disable
the tracer or 1 to enable it. Note, this only disables
writing to the ring buffer, the tracing overhead may
still be occurring.

The kernel function tracing_off() can be used within the
kernel to disable writing to the ring buffer, which will
set this file to "0". User space can re-enable tracing by
echoing "1" into the file.

Note, the function and event trigger "traceoff" will also
set this file to zero and stop tracing. Which can also
be re-enabled by user space using this file.
”h]”(hÌ)”}”(hŒëThis sets or displays whether writing to the trace
ring buffer is enabled. Echo 0 into this file to disable
the tracer or 1 to enable it. Note, this only disables
writing to the ring buffer, the tracing overhead may
still be occurring.”h]”hŒëThis sets or displays whether writing to the trace
ring buffer is enabled. Echo 0 into this file to disable
the tracer or 1 to enable it. Note, this only disables
writing to the ring buffer, the tracing overhead may
still be occurring.”…””}”(hjÝ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KnhjÙ  ubhÌ)”}”(hŒÆThe kernel function tracing_off() can be used within the
kernel to disable writing to the ring buffer, which will
set this file to "0". User space can re-enable tracing by
echoing "1" into the file.”h]”hŒÎThe kernel function tracing_off() can be used within the
kernel to disable writing to the ring buffer, which will
set this file to â€œ0â€. User space can re-enable tracing by
echoing â€œ1â€ into the file.”…””}”(hjë  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KthjÙ  ubhÌ)”}”(hŒNote, the function and event trigger "traceoff" will also
set this file to zero and stop tracing. Which can also
be re-enabled by user space using this file.”h]”hŒ¡Note, the function and event trigger â€œtraceoffâ€ will also
set this file to zero and stop tracing. Which can also
be re-enabled by user space using this file.”…””}”(hjù  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KyhjÙ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Knhj{  ubhÌ)”}”(hŒtrace:”h]”hŒtrace:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K}hj{  ubjh  )”}”(hXµ  This file holds the output of the trace in a human
readable format (described below). Opening this file for
writing with the O_TRUNC flag clears the ring buffer content.
Note, this file is not a consumer. If tracing is off
(no tracer running, or tracing_on is zero), it will produce
the same output each time it is read. When tracing is on,
it may produce inconsistent results as it tries to read
the entire buffer without consuming it.
”h]”hÌ)”}”(hX´  This file holds the output of the trace in a human
readable format (described below). Opening this file for
writing with the O_TRUNC flag clears the ring buffer content.
Note, this file is not a consumer. If tracing is off
(no tracer running, or tracing_on is zero), it will produce
the same output each time it is read. When tracing is on,
it may produce inconsistent results as it tries to read
the entire buffer without consuming it.”h]”hX´  This file holds the output of the trace in a human
readable format (described below). Opening this file for
writing with the O_TRUNC flag clears the ring buffer content.
Note, this file is not a consumer. If tracing is off
(no tracer running, or tracing_on is zero), it will produce
the same output each time it is read. When tracing is on,
it may produce inconsistent results as it tries to read
the entire buffer without consuming it.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Khj{  ubhÌ)”}”(hŒtrace_pipe:”h]”hŒtrace_pipe:”…””}”(hj3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kˆhj{  ubjh  )”}”(hX  The output is the same as the "trace" file but this
file is meant to be streamed with live tracing.
Reads from this file will block until new data is
retrieved.  Unlike the "trace" file, this file is a
consumer. This means reading from this file causes
sequential reads to display more current data. Once
data is read from this file, it is consumed, and
will not be read again with a sequential read. The
"trace" file is static, and if the tracer is not
adding more data, it will display the same
information every time it is read.
”h]”hÌ)”}”(hX  The output is the same as the "trace" file but this
file is meant to be streamed with live tracing.
Reads from this file will block until new data is
retrieved.  Unlike the "trace" file, this file is a
consumer. This means reading from this file causes
sequential reads to display more current data. Once
data is read from this file, it is consumed, and
will not be read again with a sequential read. The
"trace" file is static, and if the tracer is not
adding more data, it will display the same
information every time it is read.”h]”hX  The output is the same as the â€œtraceâ€ file but this
file is meant to be streamed with live tracing.
Reads from this file will block until new data is
retrieved.  Unlike the â€œtraceâ€ file, this file is a
consumer. This means reading from this file causes
sequential reads to display more current data. Once
data is read from this file, it is consumed, and
will not be read again with a sequential read. The
â€œtraceâ€ file is static, and if the tracer is not
adding more data, it will display the same
information every time it is read.”…””}”(hjE  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KŠhjA  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´KŠhj{  ubhÌ)”}”(hŒtrace_options:”h]”hŒtrace_options:”…””}”(hjY  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K–hj{  ubjh  )”}”(hŒÁThis file lets the user control the amount of data
that is displayed in one of the above output
files. Options also exist to modify how a tracer
or events work (stack traces, timestamps, etc).
”h]”hÌ)”}”(hŒÀThis file lets the user control the amount of data
that is displayed in one of the above output
files. Options also exist to modify how a tracer
or events work (stack traces, timestamps, etc).”h]”hŒÀThis file lets the user control the amount of data
that is displayed in one of the above output
files. Options also exist to modify how a tracer
or events work (stack traces, timestamps, etc).”…””}”(hjk  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K˜hjg  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´K˜hj{  ubhÌ)”}”(hŒoptions:”h]”hŒoptions:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj{  ubjh  )”}”(hŒØThis is a directory that has a file for every available
trace option (also in trace_options). Options may also be set
or cleared by writing a "1" or "0" respectively into the
corresponding file with the option name.
”h]”hÌ)”}”(hŒ×This is a directory that has a file for every available
trace option (also in trace_options). Options may also be set
or cleared by writing a "1" or "0" respectively into the
corresponding file with the option name.”h]”hŒßThis is a directory that has a file for every available
trace option (also in trace_options). Options may also be set
or cleared by writing a â€œ1â€ or â€œ0â€ respectively into the
corresponding file with the option name.”…””}”(hj‘  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KŸhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´KŸhj{  ubhÌ)”}”(hŒtracing_max_latency:”h]”hŒtracing_max_latency:”…””}”(hj¥  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¤hj{  ubjh  )”}”(hX¯  Some of the tracers record the max latency.
For example, the maximum time that interrupts are disabled.
The maximum time is saved in this file. The max trace will also be
stored, and displayed by "trace". A new max trace will only be
recorded if the latency is greater than the value in this file
(in microseconds).

By echoing in a time into this file, no latency will be recorded
unless it is greater than the time in this file.
”h]”(hÌ)”}”(hX;  Some of the tracers record the max latency.
For example, the maximum time that interrupts are disabled.
The maximum time is saved in this file. The max trace will also be
stored, and displayed by "trace". A new max trace will only be
recorded if the latency is greater than the value in this file
(in microseconds).”h]”hX?  Some of the tracers record the max latency.
For example, the maximum time that interrupts are disabled.
The maximum time is saved in this file. The max trace will also be
stored, and displayed by â€œtraceâ€. A new max trace will only be
recorded if the latency is greater than the value in this file
(in microseconds).”…””}”(hj·  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¦hj³  ubhÌ)”}”(hŒqBy echoing in a time into this file, no latency will be recorded
unless it is greater than the time in this file.”h]”hŒqBy echoing in a time into this file, no latency will be recorded
unless it is greater than the time in this file.”…””}”(hjÅ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K­hj³  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´K¦hj{  ubhÌ)”}”(hŒtracing_thresh:”h]”hŒtracing_thresh:”…””}”(hjÙ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K°hj{  ubjh  )”}”(hŒµSome latency tracers will record a trace whenever the
latency is greater than the number in this file.
Only active when the file contains a number greater than 0.
(in microseconds)
”h]”hÌ)”}”(hŒ´Some latency tracers will record a trace whenever the
latency is greater than the number in this file.
Only active when the file contains a number greater than 0.
(in microseconds)”h]”hŒ´Some latency tracers will record a trace whenever the
latency is greater than the number in this file.
Only active when the file contains a number greater than 0.
(in microseconds)”…””}”(hjë  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K²hjç  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´K²hj{  ubhÌ)”}”(hŒbuffer_percent:”h]”hŒbuffer_percent:”…””}”(hjÿ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K·hj{  ubjh  )”}”(hX®  This is the watermark for how much the ring buffer needs to be filled
before a waiter is woken up. That is, if an application calls a
blocking read syscall on one of the per_cpu trace_pipe_raw files, it
will block until the given amount of data specified by buffer_percent
is in the ring buffer before it wakes the reader up. This also
controls how the splice system calls are blocked on this file::

  0   - means to wake up as soon as there is any data in the ring buffer.
  50  - means to wake up when roughly half of the ring buffer sub-buffers
        are full.
  100 - means to block until the ring buffer is totally full and is
        about to start overwriting the older data.
”h]”(hÌ)”}”(hX  This is the watermark for how much the ring buffer needs to be filled
before a waiter is woken up. That is, if an application calls a
blocking read syscall on one of the per_cpu trace_pipe_raw files, it
will block until the given amount of data specified by buffer_percent
is in the ring buffer before it wakes the reader up. This also
controls how the splice system calls are blocked on this file::”h]”hXŽ  This is the watermark for how much the ring buffer needs to be filled
before a waiter is woken up. That is, if an application calls a
blocking read syscall on one of the per_cpu trace_pipe_raw files, it
will block until the given amount of data specified by buffer_percent
is in the ring buffer before it wakes the reader up. This also
controls how the splice system calls are blocked on this file:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¹hj  ubj´  )”}”(hX  0   - means to wake up as soon as there is any data in the ring buffer.
50  - means to wake up when roughly half of the ring buffer sub-buffers
      are full.
100 - means to block until the ring buffer is totally full and is
      about to start overwriting the older data.”h]”hX  0   - means to wake up as soon as there is any data in the ring buffer.
50  - means to wake up when roughly half of the ring buffer sub-buffers
      are full.
100 - means to block until the ring buffer is totally full and is
      about to start overwriting the older data.”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´KÀhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´K¹hj{  ubhÌ)”}”(hŒbuffer_size_kb:”h]”hŒbuffer_size_kb:”…””}”(hj3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÆhj{  ubjh  )”}”(hX  This sets or displays the number of kilobytes each CPU
buffer holds. By default, the trace buffers are the same size
for each CPU. The displayed number is the size of the
CPU buffer and not total size of all buffers. The
trace buffers are allocated in pages (blocks of memory
that the kernel uses for allocation, usually 4 KB in size).
A few extra pages may be allocated to accommodate buffer management
meta-data. If the last page allocated has room for more bytes
than requested, the rest of the page will be used,
making the actual allocation bigger than requested or shown.
( Note, the size may not be a multiple of the page size
due to buffer management meta-data. )

Buffer sizes for individual CPUs may vary
(see "per_cpu/cpu0/buffer_size_kb" below), and if they do
this file will show "X".
”h]”(hÌ)”}”(hXŸ  This sets or displays the number of kilobytes each CPU
buffer holds. By default, the trace buffers are the same size
for each CPU. The displayed number is the size of the
CPU buffer and not total size of all buffers. The
trace buffers are allocated in pages (blocks of memory
that the kernel uses for allocation, usually 4 KB in size).
A few extra pages may be allocated to accommodate buffer management
meta-data. If the last page allocated has room for more bytes
than requested, the rest of the page will be used,
making the actual allocation bigger than requested or shown.
( Note, the size may not be a multiple of the page size
due to buffer management meta-data. )”h]”hXŸ  This sets or displays the number of kilobytes each CPU
buffer holds. By default, the trace buffers are the same size
for each CPU. The displayed number is the size of the
CPU buffer and not total size of all buffers. The
trace buffers are allocated in pages (blocks of memory
that the kernel uses for allocation, usually 4 KB in size).
A few extra pages may be allocated to accommodate buffer management
meta-data. If the last page allocated has room for more bytes
than requested, the rest of the page will be used,
making the actual allocation bigger than requested or shown.
( Note, the size may not be a multiple of the page size
due to buffer management meta-data. )”…””}”(hjE  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÈhjA  ubhÌ)”}”(hŒ|Buffer sizes for individual CPUs may vary
(see "per_cpu/cpu0/buffer_size_kb" below), and if they do
this file will show "X".”h]”hŒ„Buffer sizes for individual CPUs may vary
(see â€œper_cpu/cpu0/buffer_size_kbâ€ below), and if they do
this file will show â€œXâ€.”…””}”(hjS  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÕhjA  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´KÈhj{  ubhÌ)”}”(hŒbuffer_total_size_kb:”h]”hŒbuffer_total_size_kb:”…””}”(hjg  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÙhj{  ubjh  )”}”(hŒ@This displays the total combined size of all the trace buffers.
”h]”hÌ)”}”(hŒ?This displays the total combined size of all the trace buffers.”h]”hŒ?This displays the total combined size of all the trace buffers.”…””}”(hjy  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÛhju  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´KÛhj{  ubhÌ)”}”(hŒbuffer_subbuf_size_kb:”h]”hŒbuffer_subbuf_size_kb:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÝhj{  ubjh  )”}”(hX“  This sets or displays the sub buffer size. The ring buffer is broken up
into several same size "sub buffers". An event can not be bigger than
the size of the sub buffer. Normally, the sub buffer is the size of the
architecture's page (4K on x86). The sub buffer also contains meta data
at the start which also limits the size of an event.  That means when
the sub buffer is a page size, no event can be larger than the page
size minus the sub buffer meta data.

Note, the buffer_subbuf_size_kb is a way for the user to specify the
minimum size of the subbuffer. The kernel may make it bigger due to the
implementation details, or simply fail the operation if the kernel can
not handle the request.

Changing the sub buffer size allows for events to be larger than the
page size.

Note: When changing the sub-buffer size, tracing is stopped and any
data in the ring buffer and the snapshot buffer will be discarded.
”h]”(hÌ)”}”(hXÌ  This sets or displays the sub buffer size. The ring buffer is broken up
into several same size "sub buffers". An event can not be bigger than
the size of the sub buffer. Normally, the sub buffer is the size of the
architecture's page (4K on x86). The sub buffer also contains meta data
at the start which also limits the size of an event.  That means when
the sub buffer is a page size, no event can be larger than the page
size minus the sub buffer meta data.”h]”hXÒ  This sets or displays the sub buffer size. The ring buffer is broken up
into several same size â€œsub buffersâ€. An event can not be bigger than
the size of the sub buffer. Normally, the sub buffer is the size of the
architectureâ€™s page (4K on x86). The sub buffer also contains meta data
at the start which also limits the size of an event.  That means when
the sub buffer is a page size, no event can be larger than the page
size minus the sub buffer meta data.”…””}”(hjŸ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kßhj›  ubhÌ)”}”(hŒëNote, the buffer_subbuf_size_kb is a way for the user to specify the
minimum size of the subbuffer. The kernel may make it bigger due to the
implementation details, or simply fail the operation if the kernel can
not handle the request.”h]”hŒëNote, the buffer_subbuf_size_kb is a way for the user to specify the
minimum size of the subbuffer. The kernel may make it bigger due to the
implementation details, or simply fail the operation if the kernel can
not handle the request.”…””}”(hj­  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kçhj›  ubhÌ)”}”(hŒOChanging the sub buffer size allows for events to be larger than the
page size.”h]”hŒOChanging the sub buffer size allows for events to be larger than the
page size.”…””}”(hj»  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kìhj›  ubhÌ)”}”(hŒ†Note: When changing the sub-buffer size, tracing is stopped and any
data in the ring buffer and the snapshot buffer will be discarded.”h]”hŒ†Note: When changing the sub-buffer size, tracing is stopped and any
data in the ring buffer and the snapshot buffer will be discarded.”…””}”(hjÉ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kïhj›  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Kßhj{  ubhÌ)”}”(hŒfree_buffer:”h]”hŒfree_buffer:”…””}”(hjÝ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kòhj{  ubjh  )”}”(hXú  If a process is performing tracing, and the ring buffer should be
shrunk "freed" when the process is finished, even if it were to be
killed by a signal, this file can be used for that purpose. On close
of this file, the ring buffer will be resized to its minimum size.
Having a process that is tracing also open this file, when the process
exits its file descriptor for this file will be closed, and in doing so,
the ring buffer will be "freed".

It may also stop tracing if disable_on_free option is set.
”h]”(hÌ)”}”(hX½  If a process is performing tracing, and the ring buffer should be
shrunk "freed" when the process is finished, even if it were to be
killed by a signal, this file can be used for that purpose. On close
of this file, the ring buffer will be resized to its minimum size.
Having a process that is tracing also open this file, when the process
exits its file descriptor for this file will be closed, and in doing so,
the ring buffer will be "freed".”h]”hXÅ  If a process is performing tracing, and the ring buffer should be
shrunk â€œfreedâ€ when the process is finished, even if it were to be
killed by a signal, this file can be used for that purpose. On close
of this file, the ring buffer will be resized to its minimum size.
Having a process that is tracing also open this file, when the process
exits its file descriptor for this file will be closed, and in doing so,
the ring buffer will be â€œfreedâ€.”…””}”(hjï  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kôhjë  ubhÌ)”}”(hŒ:It may also stop tracing if disable_on_free option is set.”h]”hŒ:It may also stop tracing if disable_on_free option is set.”…””}”(hjý  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kühjë  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Kôhj{  ubhÌ)”}”(hŒtracing_cpumask:”h]”hŒtracing_cpumask:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kþhj{  ubjh  )”}”(hŒrThis is a mask that lets the user only trace on specified CPUs.
The format is a hex string representing the CPUs.
”h]”hÌ)”}”(hŒqThis is a mask that lets the user only trace on specified CPUs.
The format is a hex string representing the CPUs.”h]”hŒqThis is a mask that lets the user only trace on specified CPUs.
The format is a hex string representing the CPUs.”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M hj{  ubhÌ)”}”(hŒset_ftrace_filter:”h]”hŒset_ftrace_filter:”…””}”(hj7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hX;  When dynamic ftrace is configured in (see the
section below "dynamic ftrace"), the code is dynamically
modified (code text rewrite) to disable calling of the
function profiler (mcount). This lets tracing be configured
in with practically no overhead in performance.  This also
has a side effect of enabling or disabling specific functions
to be traced. Echoing names of functions into this file
will limit the trace to only those functions.
This influences the tracers "function" and "function_graph"
and thus also function profiling (see "function_profile_enabled").

The functions listed in "available_filter_functions" are what
can be written into this file.

This interface also allows for commands to be used. See the
"Filter commands" section for more details.

As a speed up, since processing strings can be quite expensive
and requires a check of all functions registered to tracing, instead
an index can be written into this file. A number (starting with "1")
written will instead select the same corresponding at the line position
of the "available_filter_functions" file.
”h]”(hÌ)”}”(hX7  When dynamic ftrace is configured in (see the
section below "dynamic ftrace"), the code is dynamically
modified (code text rewrite) to disable calling of the
function profiler (mcount). This lets tracing be configured
in with practically no overhead in performance.  This also
has a side effect of enabling or disabling specific functions
to be traced. Echoing names of functions into this file
will limit the trace to only those functions.
This influences the tracers "function" and "function_graph"
and thus also function profiling (see "function_profile_enabled").”h]”hXG  When dynamic ftrace is configured in (see the
section below â€œdynamic ftraceâ€), the code is dynamically
modified (code text rewrite) to disable calling of the
function profiler (mcount). This lets tracing be configured
in with practically no overhead in performance.  This also
has a side effect of enabling or disabling specific functions
to be traced. Echoing names of functions into this file
will limit the trace to only those functions.
This influences the tracers â€œfunctionâ€ and â€œfunction_graphâ€
and thus also function profiling (see â€œfunction_profile_enabledâ€).”…””}”(hjI  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjE  ubhÌ)”}”(hŒ\The functions listed in "available_filter_functions" are what
can be written into this file.”h]”hŒ`The functions listed in â€œavailable_filter_functionsâ€ are what
can be written into this file.”…””}”(hjW  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjE  ubhÌ)”}”(hŒgThis interface also allows for commands to be used. See the
"Filter commands" section for more details.”h]”hŒkThis interface also allows for commands to be used. See the
â€œFilter commandsâ€ section for more details.”…””}”(hje  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjE  ubhÌ)”}”(hX:  As a speed up, since processing strings can be quite expensive
and requires a check of all functions registered to tracing, instead
an index can be written into this file. A number (starting with "1")
written will instead select the same corresponding at the line position
of the "available_filter_functions" file.”h]”hXB  As a speed up, since processing strings can be quite expensive
and requires a check of all functions registered to tracing, instead
an index can be written into this file. A number (starting with â€œ1â€)
written will instead select the same corresponding at the line position
of the â€œavailable_filter_functionsâ€ file.”…””}”(hjs  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjE  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒset_ftrace_notrace:”h]”hŒset_ftrace_notrace:”…””}”(hj‡  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hŒØThis has an effect opposite to that of
set_ftrace_filter. Any function that is added here will not
be traced. If a function exists in both set_ftrace_filter
and set_ftrace_notrace, the function will _not_ be traced.
”h]”hÌ)”}”(hŒ×This has an effect opposite to that of
set_ftrace_filter. Any function that is added here will not
be traced. If a function exists in both set_ftrace_filter
and set_ftrace_notrace, the function will _not_ be traced.”h]”hŒ×This has an effect opposite to that of
set_ftrace_filter. Any function that is added here will not
be traced. If a function exists in both set_ftrace_filter
and set_ftrace_notrace, the function will _not_ be traced.”…””}”(hj™  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj•  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒset_ftrace_pid:”h]”hŒset_ftrace_pid:”…””}”(hj­  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M#hj{  ubjh  )”}”(hX{  Have the function tracer only trace the threads whose PID are
listed in this file.

If the "function-fork" option is set, then when a task whose
PID is listed in this file forks, the child's PID will
automatically be added to this file, and the child will be
traced by the function tracer as well. This option will also
cause PIDs of tasks that exit to be removed from the file.
”h]”(hÌ)”}”(hŒRHave the function tracer only trace the threads whose PID are
listed in this file.”h]”hŒRHave the function tracer only trace the threads whose PID are
listed in this file.”…””}”(hj¿  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M%hj»  ubhÌ)”}”(hX&  If the "function-fork" option is set, then when a task whose
PID is listed in this file forks, the child's PID will
automatically be added to this file, and the child will be
traced by the function tracer as well. This option will also
cause PIDs of tasks that exit to be removed from the file.”h]”hX,  If the â€œfunction-forkâ€ option is set, then when a task whose
PID is listed in this file forks, the childâ€™s PID will
automatically be added to this file, and the child will be
traced by the function tracer as well. This option will also
cause PIDs of tasks that exit to be removed from the file.”…””}”(hjÍ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M(hj»  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M%hj{  ubhÌ)”}”(hŒset_ftrace_notrace_pid:”h]”hŒset_ftrace_notrace_pid:”…””}”(hjá  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M.hj{  ubjh  )”}”(hXð  Have the function tracer ignore threads whose PID are listed in
this file.

If the "function-fork" option is set, then when a task whose
PID is listed in this file forks, the child's PID will
automatically be added to this file, and the child will not be
traced by the function tracer as well. This option will also
cause PIDs of tasks that exit to be removed from the file.

If a PID is in both this file and "set_ftrace_pid", then this
file takes precedence, and the thread will not be traced.
”h]”(hÌ)”}”(hŒJHave the function tracer ignore threads whose PID are listed in
this file.”h]”hŒJHave the function tracer ignore threads whose PID are listed in
this file.”…””}”(hjó  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M0hjï  ubhÌ)”}”(hX*  If the "function-fork" option is set, then when a task whose
PID is listed in this file forks, the child's PID will
automatically be added to this file, and the child will not be
traced by the function tracer as well. This option will also
cause PIDs of tasks that exit to be removed from the file.”h]”hX0  If the â€œfunction-forkâ€ option is set, then when a task whose
PID is listed in this file forks, the childâ€™s PID will
automatically be added to this file, and the child will not be
traced by the function tracer as well. This option will also
cause PIDs of tasks that exit to be removed from the file.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M3hjï  ubhÌ)”}”(hŒwIf a PID is in both this file and "set_ftrace_pid", then this
file takes precedence, and the thread will not be traced.”h]”hŒ{If a PID is in both this file and â€œset_ftrace_pidâ€, then this
file takes precedence, and the thread will not be traced.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M9hjï  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M0hj{  ubhÌ)”}”(hŒset_event_pid:”h]”hŒset_event_pid:”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M<hj{  ubjh  )”}”(hXe  Have the events only trace a task with a PID listed in this file.
Note, sched_switch and sched_wake_up will also trace events
listed in this file.

To have the PIDs of children of tasks with their PID in this file
added on fork, enable the "event-fork" option. That option will also
cause the PIDs of tasks to be removed from this file when the task
exits.
”h]”(hÌ)”}”(hŒ’Have the events only trace a task with a PID listed in this file.
Note, sched_switch and sched_wake_up will also trace events
listed in this file.”h]”hŒ’Have the events only trace a task with a PID listed in this file.
Note, sched_switch and sched_wake_up will also trace events
listed in this file.”…””}”(hj5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M>hj1  ubhÌ)”}”(hŒÐTo have the PIDs of children of tasks with their PID in this file
added on fork, enable the "event-fork" option. That option will also
cause the PIDs of tasks to be removed from this file when the task
exits.”h]”hŒÔTo have the PIDs of children of tasks with their PID in this file
added on fork, enable the â€œevent-forkâ€ option. That option will also
cause the PIDs of tasks to be removed from this file when the task
exits.”…””}”(hjC  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MBhj1  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M>hj{  ubhÌ)”}”(hŒset_event_notrace_pid:”h]”hŒset_event_notrace_pid:”…””}”(hjW  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MGhj{  ubjh  )”}”(hXß  Have the events not trace a task with a PID listed in this file.
Note, sched_switch and sched_wakeup will trace threads not listed
in this file, even if a thread's PID is in the file if the
sched_switch or sched_wakeup events also trace a thread that should
be traced.

To have the PIDs of children of tasks with their PID in this file
added on fork, enable the "event-fork" option. That option will also
cause the PIDs of tasks to be removed from this file when the task
exits.
”h]”(hÌ)”}”(hX  Have the events not trace a task with a PID listed in this file.
Note, sched_switch and sched_wakeup will trace threads not listed
in this file, even if a thread's PID is in the file if the
sched_switch or sched_wakeup events also trace a thread that should
be traced.”h]”hX  Have the events not trace a task with a PID listed in this file.
Note, sched_switch and sched_wakeup will trace threads not listed
in this file, even if a threadâ€™s PID is in the file if the
sched_switch or sched_wakeup events also trace a thread that should
be traced.”…””}”(hji  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MIhje  ubhÌ)”}”(hŒÐTo have the PIDs of children of tasks with their PID in this file
added on fork, enable the "event-fork" option. That option will also
cause the PIDs of tasks to be removed from this file when the task
exits.”h]”hŒÔTo have the PIDs of children of tasks with their PID in this file
added on fork, enable the â€œevent-forkâ€ option. That option will also
cause the PIDs of tasks to be removed from this file when the task
exits.”…””}”(hjw  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MOhje  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MIhj{  ubhÌ)”}”(hŒset_graph_function:”h]”hŒset_graph_function:”…””}”(hj‹  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MThj{  ubjh  )”}”(hX  Functions listed in this file will cause the function graph
tracer to only trace these functions and the functions that
they call. (See the section "dynamic ftrace" for more details).
Note, set_ftrace_filter and set_ftrace_notrace still affects
what functions are being traced.
”h]”hÌ)”}”(hX  Functions listed in this file will cause the function graph
tracer to only trace these functions and the functions that
they call. (See the section "dynamic ftrace" for more details).
Note, set_ftrace_filter and set_ftrace_notrace still affects
what functions are being traced.”h]”hX  Functions listed in this file will cause the function graph
tracer to only trace these functions and the functions that
they call. (See the section â€œdynamic ftraceâ€ for more details).
Note, set_ftrace_filter and set_ftrace_notrace still affects
what functions are being traced.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MVhj™  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MVhj{  ubhÌ)”}”(hŒset_graph_notrace:”h]”hŒset_graph_notrace:”…””}”(hj±  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M\hj{  ubjh  )”}”(hŒØSimilar to set_graph_function, but will disable function graph
tracing when the function is hit until it exits the function.
This makes it possible to ignore tracing functions that are called
by a specific function.
”h]”hÌ)”}”(hŒ×Similar to set_graph_function, but will disable function graph
tracing when the function is hit until it exits the function.
This makes it possible to ignore tracing functions that are called
by a specific function.”h]”hŒ×Similar to set_graph_function, but will disable function graph
tracing when the function is hit until it exits the function.
This makes it possible to ignore tracing functions that are called
by a specific function.”…””}”(hjÃ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M^hj¿  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M^hj{  ubhÌ)”}”(hŒavailable_filter_functions:”h]”hŒavailable_filter_functions:”…””}”(hj×  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mchj{  ubjh  )”}”(hX  This lists the functions that ftrace has processed and can trace.
These are the function names that you can pass to
"set_ftrace_filter", "set_ftrace_notrace",
"set_graph_function", or "set_graph_notrace".
(See the section "dynamic ftrace" below for more details.)
”h]”hÌ)”}”(hX  This lists the functions that ftrace has processed and can trace.
These are the function names that you can pass to
"set_ftrace_filter", "set_ftrace_notrace",
"set_graph_function", or "set_graph_notrace".
(See the section "dynamic ftrace" below for more details.)”h]”hX  This lists the functions that ftrace has processed and can trace.
These are the function names that you can pass to
â€œset_ftrace_filterâ€, â€œset_ftrace_notraceâ€,
â€œset_graph_functionâ€, or â€œset_graph_notraceâ€.
(See the section â€œdynamic ftraceâ€ below for more details.)”…””}”(hjé  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mehjå  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mehj{  ubhÌ)”}”(hŒ!available_filter_functions_addrs:”h]”hŒ!available_filter_functions_addrs:”…””}”(hjý  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mkhj{  ubjh  )”}”(hŒ±Similar to available_filter_functions, but with address displayed
for each function. The displayed address is the patch-site address
and can differ from /proc/kallsyms address.
”h]”hÌ)”}”(hŒ°Similar to available_filter_functions, but with address displayed
for each function. The displayed address is the patch-site address
and can differ from /proc/kallsyms address.”h]”hŒ°Similar to available_filter_functions, but with address displayed
for each function. The displayed address is the patch-site address
and can differ from /proc/kallsyms address.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mmhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mmhj{  ubhÌ)”}”(hŒsyscall_user_buf_size:”h]”hŒsyscall_user_buf_size:”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mqhj{  ubjh  )”}”(hX!  Some system call trace events will record the data from a user
space address that one of the parameters point to. The amount of
data per event is limited. This file holds the max number of bytes
that will be recorded into the ring buffer to hold this data.
The max value is currently 165.
”h]”hÌ)”}”(hX   Some system call trace events will record the data from a user
space address that one of the parameters point to. The amount of
data per event is limited. This file holds the max number of bytes
that will be recorded into the ring buffer to hold this data.
The max value is currently 165.”h]”hX   Some system call trace events will record the data from a user
space address that one of the parameters point to. The amount of
data per event is limited. This file holds the max number of bytes
that will be recorded into the ring buffer to hold this data.
The max value is currently 165.”…””}”(hj5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mshj1  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mshj{  ubhÌ)”}”(hŒdyn_ftrace_total_info:”h]”hŒdyn_ftrace_total_info:”…””}”(hjI  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Myhj{  ubjh  )”}”(hŒ~This file is for debugging purposes. The number of functions that
have been converted to nops and are available to be traced.
”h]”hÌ)”}”(hŒ}This file is for debugging purposes. The number of functions that
have been converted to nops and are available to be traced.”h]”hŒ}This file is for debugging purposes. The number of functions that
have been converted to nops and are available to be traced.”…””}”(hj[  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M{hjW  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M{hj{  ubhÌ)”}”(hŒenabled_functions:”h]”hŒenabled_functions:”…””}”(hjo  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M~hj{  ubjh  )”}”(hXQ  This file is more for debugging ftrace, but can also be useful
in seeing if any function has a callback attached to it.
Not only does the trace infrastructure use ftrace function
trace utility, but other subsystems might too. This file
displays all functions that have a callback attached to them
as well as the number of callbacks that have been attached.
Note, a callback may also call multiple functions which will
not be listed in this count.

If the callback registered to be traced by a function with
the "save regs" attribute (thus even more overhead), an 'R'
will be displayed on the same line as the function that
is returning registers.

If the callback registered to be traced by a function with
the "ip modify" attribute (thus the regs->ip can be changed),
an 'I' will be displayed on the same line as the function that
can be overridden.

If a non-ftrace trampoline is attached (BPF) a 'D' will be displayed.
Note, normal ftrace trampolines can also be attached, but only one
"direct" trampoline can be attached to a given function at a time.

Some architectures can not call direct trampolines, but instead have
the ftrace ops function located above the function entry point. In
such cases an 'O' will be displayed.

If a function had either the "ip modify" or a "direct" call attached to
it in the past, a 'M' will be shown. This flag is never cleared. It is
used to know if a function was ever modified by the ftrace infrastructure,
and can be used for debugging.

If the architecture supports it, it will also show what callback
is being directly called by the function. If the count is greater
than 1 it most likely will be ftrace_ops_list_func().

If the callback of a function jumps to a trampoline that is
specific to the callback and which is not the standard trampoline,
its address will be printed as well as the function that the
trampoline calls.
”h]”(hÌ)”}”(hX¾  This file is more for debugging ftrace, but can also be useful
in seeing if any function has a callback attached to it.
Not only does the trace infrastructure use ftrace function
trace utility, but other subsystems might too. This file
displays all functions that have a callback attached to them
as well as the number of callbacks that have been attached.
Note, a callback may also call multiple functions which will
not be listed in this count.”h]”hX¾  This file is more for debugging ftrace, but can also be useful
in seeing if any function has a callback attached to it.
Not only does the trace infrastructure use ftrace function
trace utility, but other subsystems might too. This file
displays all functions that have a callback attached to them
as well as the number of callbacks that have been attached.
Note, a callback may also call multiple functions which will
not be listed in this count.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M€hj}  ubhÌ)”}”(hŒÆIf the callback registered to be traced by a function with
the "save regs" attribute (thus even more overhead), an 'R'
will be displayed on the same line as the function that
is returning registers.”h]”hŒÎIf the callback registered to be traced by a function with
the â€œsave regsâ€ attribute (thus even more overhead), an â€˜Râ€™
will be displayed on the same line as the function that
is returning registers.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‰hj}  ubhÌ)”}”(hŒÊIf the callback registered to be traced by a function with
the "ip modify" attribute (thus the regs->ip can be changed),
an 'I' will be displayed on the same line as the function that
can be overridden.”h]”hŒÒIf the callback registered to be traced by a function with
the â€œip modifyâ€ attribute (thus the regs->ip can be changed),
an â€˜Iâ€™ will be displayed on the same line as the function that
can be overridden.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŽhj}  ubhÌ)”}”(hŒËIf a non-ftrace trampoline is attached (BPF) a 'D' will be displayed.
Note, normal ftrace trampolines can also be attached, but only one
"direct" trampoline can be attached to a given function at a time.”h]”hŒÓIf a non-ftrace trampoline is attached (BPF) a â€˜Dâ€™ will be displayed.
Note, normal ftrace trampolines can also be attached, but only one
â€œdirectâ€ trampoline can be attached to a given function at a time.”…””}”(hj«  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M“hj}  ubhÌ)”}”(hŒ¬Some architectures can not call direct trampolines, but instead have
the ftrace ops function located above the function entry point. In
such cases an 'O' will be displayed.”h]”hŒ°Some architectures can not call direct trampolines, but instead have
the ftrace ops function located above the function entry point. In
such cases an â€˜Oâ€™ will be displayed.”…””}”(hj¹  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M—hj}  ubhÌ)”}”(hŒøIf a function had either the "ip modify" or a "direct" call attached to
it in the past, a 'M' will be shown. This flag is never cleared. It is
used to know if a function was ever modified by the ftrace infrastructure,
and can be used for debugging.”h]”hX  If a function had either the â€œip modifyâ€ or a â€œdirectâ€ call attached to
it in the past, a â€˜Mâ€™ will be shown. This flag is never cleared. It is
used to know if a function was ever modified by the ftrace infrastructure,
and can be used for debugging.”…””}”(hjÇ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M›hj}  ubhÌ)”}”(hŒ¸If the architecture supports it, it will also show what callback
is being directly called by the function. If the count is greater
than 1 it most likely will be ftrace_ops_list_func().”h]”hŒ¸If the architecture supports it, it will also show what callback
is being directly called by the function. If the count is greater
than 1 it most likely will be ftrace_ops_list_func().”…””}”(hjÕ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hj}  ubhÌ)”}”(hŒÍIf the callback of a function jumps to a trampoline that is
specific to the callback and which is not the standard trampoline,
its address will be printed as well as the function that the
trampoline calls.”h]”hŒÍIf the callback of a function jumps to a trampoline that is
specific to the callback and which is not the standard trampoline,
its address will be printed as well as the function that the
trampoline calls.”…””}”(hjã  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¤hj}  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M€hj{  ubhÌ)”}”(hŒtouched_functions:”h]”hŒtouched_functions:”…””}”(hj÷  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M©hj{  ubjh  )”}”(hX~  This file contains all the functions that ever had a function callback
to it via the ftrace infrastructure. It has the same format as
enabled_functions but shows all functions that have ever been
traced.

To see any function that has every been modified by "ip modify" or a
direct trampoline, one can perform the following command:

grep ' M ' /sys/kernel/tracing/touched_functions
”h]”(hÌ)”}”(hŒËThis file contains all the functions that ever had a function callback
to it via the ftrace infrastructure. It has the same format as
enabled_functions but shows all functions that have ever been
traced.”h]”hŒËThis file contains all the functions that ever had a function callback
to it via the ftrace infrastructure. It has the same format as
enabled_functions but shows all functions that have ever been
traced.”…””}”(hj		  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M«hj	  ubhÌ)”}”(hŒ~To see any function that has every been modified by "ip modify" or a
direct trampoline, one can perform the following command:”h]”hŒ‚To see any function that has every been modified by â€œip modifyâ€ or a
direct trampoline, one can perform the following command:”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M°hj	  ubhÌ)”}”(hŒ0grep ' M ' /sys/kernel/tracing/touched_functions”h]”hŒ4grep â€˜ M â€˜ /sys/kernel/tracing/touched_functions”…””}”(hj%	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M³hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M«hj{  ubhÌ)”}”(hŒfunction_profile_enabled:”h]”hŒfunction_profile_enabled:”…””}”(hj9	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mµhj{  ubjh  )”}”(hX•  When set it will enable all functions with either the function
tracer, or if configured, the function graph tracer. It will
keep a histogram of the number of functions that were called
and if the function graph tracer was configured, it will also keep
track of the time spent in those functions. The histogram
content can be displayed in the files:

trace_stat/function<cpu> ( function0, function1, etc).
”h]”(hÌ)”}”(hX\  When set it will enable all functions with either the function
tracer, or if configured, the function graph tracer. It will
keep a histogram of the number of functions that were called
and if the function graph tracer was configured, it will also keep
track of the time spent in those functions. The histogram
content can be displayed in the files:”h]”hX\  When set it will enable all functions with either the function
tracer, or if configured, the function graph tracer. It will
keep a histogram of the number of functions that were called
and if the function graph tracer was configured, it will also keep
track of the time spent in those functions. The histogram
content can be displayed in the files:”…””}”(hjK	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M·hjG	  ubhÌ)”}”(hŒ6trace_stat/function<cpu> ( function0, function1, etc).”h]”hŒ6trace_stat/function<cpu> ( function0, function1, etc).”…””}”(hjY	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¾hjG	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M·hj{  ubhÌ)”}”(hŒtrace_stat:”h]”hŒtrace_stat:”…””}”(hjm	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÀhj{  ubjh  )”}”(hŒ0A directory that holds different tracing stats.
”h]”hÌ)”}”(hŒ/A directory that holds different tracing stats.”h]”hŒ/A directory that holds different tracing stats.”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÂhj{	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÂhj{  ubhÌ)”}”(hŒkprobe_events:”h]”hŒkprobe_events:”…””}”(hj“	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÄhj{  ubjh  )”}”(hŒ2Enable dynamic trace points. See kprobetrace.rst.
”h]”hÌ)”}”(hŒ1Enable dynamic trace points. See kprobetrace.rst.”h]”hŒ1Enable dynamic trace points. See kprobetrace.rst.”…””}”(hj¥	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÆhj¡	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÆhj{  ubhÌ)”}”(hŒkprobe_profile:”h]”hŒkprobe_profile:”…””}”(hj¹	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÈhj{  ubjh  )”}”(hŒ1Dynamic trace points stats. See kprobetrace.rst.
”h]”hÌ)”}”(hŒ0Dynamic trace points stats. See kprobetrace.rst.”h]”hŒ0Dynamic trace points stats. See kprobetrace.rst.”…””}”(hjË	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÊhjÇ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÊhj{  ubhÌ)”}”(hŒmax_graph_depth:”h]”hŒmax_graph_depth:”…””}”(hjß	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÌhj{  ubjh  )”}”(hŒÂUsed with the function graph tracer. This is the max depth
it will trace into a function. Setting this to a value of
one will show only the first kernel function that is called
from user space.
”h]”hÌ)”}”(hŒÁUsed with the function graph tracer. This is the max depth
it will trace into a function. Setting this to a value of
one will show only the first kernel function that is called
from user space.”h]”hŒÁUsed with the function graph tracer. This is the max depth
it will trace into a function. Setting this to a value of
one will show only the first kernel function that is called
from user space.”…””}”(hjñ	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÎhjí	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÎhj{  ubhÌ)”}”(hŒprintk_formats:”h]”hŒprintk_formats:”…””}”(hj
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÓhj{  ubjh  )”}”(hXg  This is for tools that read the raw format files. If an event in
the ring buffer references a string, only a pointer to the string
is recorded into the buffer and not the string itself. This prevents
tools from knowing what that string was. This file displays the string
and address for the string allowing tools to map the pointers to what
the strings were.
”h]”hÌ)”}”(hXf  This is for tools that read the raw format files. If an event in
the ring buffer references a string, only a pointer to the string
is recorded into the buffer and not the string itself. This prevents
tools from knowing what that string was. This file displays the string
and address for the string allowing tools to map the pointers to what
the strings were.”h]”hXf  This is for tools that read the raw format files. If an event in
the ring buffer references a string, only a pointer to the string
is recorded into the buffer and not the string itself. This prevents
tools from knowing what that string was. This file displays the string
and address for the string allowing tools to map the pointers to what
the strings were.”…””}”(hj
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÕhj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÕhj{  ubhÌ)”}”(hŒsaved_cmdlines:”h]”hŒsaved_cmdlines:”…””}”(hj+
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÜhj{  ubjh  )”}”(hX  Only the pid of the task is recorded in a trace event unless
the event specifically saves the task comm as well. Ftrace
makes a cache of pid mappings to comms to try to display
comms for events. If a pid for a comm is not listed, then
"<...>" is displayed in the output.

If the option "record-cmd" is set to "0", then comms of tasks
will not be saved during recording. By default, it is enabled.
”h]”(hÌ)”}”(hX  Only the pid of the task is recorded in a trace event unless
the event specifically saves the task comm as well. Ftrace
makes a cache of pid mappings to comms to try to display
comms for events. If a pid for a comm is not listed, then
"<...>" is displayed in the output.”h]”hX  Only the pid of the task is recorded in a trace event unless
the event specifically saves the task comm as well. Ftrace
makes a cache of pid mappings to comms to try to display
comms for events. If a pid for a comm is not listed, then
â€œ<...>â€ is displayed in the output.”…””}”(hj=
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÞhj9
  ubhÌ)”}”(hŒ|If the option "record-cmd" is set to "0", then comms of tasks
will not be saved during recording. By default, it is enabled.”h]”hŒ„If the option â€œrecord-cmdâ€ is set to â€œ0â€, then comms of tasks
will not be saved during recording. By default, it is enabled.”…””}”(hjK
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mähj9
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÞhj{  ubhÌ)”}”(hŒsaved_cmdlines_size:”h]”hŒsaved_cmdlines_size:”…””}”(hj_
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mçhj{  ubjh  )”}”(hŒ­By default, 128 comms are saved (see "saved_cmdlines" above). To
increase or decrease the amount of comms that are cached, echo
the number of comms to cache into this file.
”h]”hÌ)”}”(hŒ¬By default, 128 comms are saved (see "saved_cmdlines" above). To
increase or decrease the amount of comms that are cached, echo
the number of comms to cache into this file.”h]”hŒ°By default, 128 comms are saved (see â€œsaved_cmdlinesâ€ above). To
increase or decrease the amount of comms that are cached, echo
the number of comms to cache into this file.”…””}”(hjq
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Méhjm
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Méhj{  ubhÌ)”}”(hŒsaved_tgids:”h]”hŒsaved_tgids:”…””}”(hj…
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Míhj{  ubjh  )”}”(hŒÓIf the option "record-tgid" is set, on each scheduling context switch
the Task Group ID of a task is saved in a table mapping the PID of
the thread to its TGID. By default, the "record-tgid" option is
disabled.
”h]”hÌ)”}”(hŒÒIf the option "record-tgid" is set, on each scheduling context switch
the Task Group ID of a task is saved in a table mapping the PID of
the thread to its TGID. By default, the "record-tgid" option is
disabled.”h]”hŒÚIf the option â€œrecord-tgidâ€ is set, on each scheduling context switch
the Task Group ID of a task is saved in a table mapping the PID of
the thread to its TGID. By default, the â€œrecord-tgidâ€ option is
disabled.”…””}”(hj—
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mïhj“
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mïhj{  ubhÌ)”}”(hŒ	snapshot:”h]”hŒ	snapshot:”…””}”(hj«
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Môhj{  ubjh  )”}”(hŒœThis displays the "snapshot" buffer and also lets the user
take a snapshot of the current running trace.
See the "Snapshot" section below for more details.
”h]”hÌ)”}”(hŒ›This displays the "snapshot" buffer and also lets the user
take a snapshot of the current running trace.
See the "Snapshot" section below for more details.”h]”hŒ£This displays the â€œsnapshotâ€ buffer and also lets the user
take a snapshot of the current running trace.
See the â€œSnapshotâ€ section below for more details.”…””}”(hj½
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Möhj¹
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Möhj{  ubhÌ)”}”(hŒstack_max_size:”h]”hŒstack_max_size:”…””}”(hjÑ
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Múhj{  ubjh  )”}”(hŒ†When the stack tracer is activated, this will display the
maximum stack size it has encountered.
See the "Stack Trace" section below.
”h]”hÌ)”}”(hŒ…When the stack tracer is activated, this will display the
maximum stack size it has encountered.
See the "Stack Trace" section below.”h]”hŒ‰When the stack tracer is activated, this will display the
maximum stack size it has encountered.
See the â€œStack Traceâ€ section below.”…””}”(hjã
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mühjß
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mühj{  ubhÌ)”}”(hŒstack_trace:”h]”hŒstack_trace:”…””}”(hj÷
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hj{  ubjh  )”}”(hŒ–This displays the stack back trace of the largest stack
that was encountered when the stack tracer is activated.
See the "Stack Trace" section below.
”h]”hÌ)”}”(hŒ•This displays the stack back trace of the largest stack
that was encountered when the stack tracer is activated.
See the "Stack Trace" section below.”h]”hŒ™This displays the stack back trace of the largest stack
that was encountered when the stack tracer is activated.
See the â€œStack Traceâ€ section below.”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒstack_trace_filter:”h]”hŒstack_trace_filter:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hŒaThis is similar to "set_ftrace_filter" but it limits what
functions the stack tracer will check.
”h]”hÌ)”}”(hŒ`This is similar to "set_ftrace_filter" but it limits what
functions the stack tracer will check.”h]”hŒdThis is similar to â€œset_ftrace_filterâ€ but it limits what
functions the stack tracer will check.”…””}”(hj/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒtrace_clock:”h]”hŒtrace_clock:”…””}”(hjC  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hX\  Whenever an event is recorded into the ring buffer, a
"timestamp" is added. This stamp comes from a specified
clock. By default, ftrace uses the "local" clock. This
clock is very fast and strictly per CPU, but on some
systems it may not be monotonic with respect to other
CPUs. In other words, the local clocks may not be in sync
with local clocks on other CPUs.

Usual clocks for tracing::

  # cat trace_clock
  [local] global counter x86-tsc

The clock with the square brackets around it is the one in effect.

local:
        Default clock, but may not be in sync across CPUs

global:
        This clock is in sync with all CPUs but may
        be a bit slower than the local clock.

counter:
        This is not a clock at all, but literally an atomic
        counter. It counts up one by one, but is in sync
        with all CPUs. This is useful when you need to
        know exactly the order events occurred with respect to
        each other on different CPUs.

uptime:
        This uses the jiffies counter and the time stamp
        is relative to the time since boot up.

perf:
        This makes ftrace use the same clock that perf uses.
        Eventually perf will be able to read ftrace buffers
        and this will help out in interleaving the data.

x86-tsc:
        Architectures may define their own clocks. For
        example, x86 uses its own TSC cycle clock here.

ppc-tb:
        This uses the powerpc timebase register value.
        This is in sync across CPUs and can also be used
        to correlate events across hypervisor/guest if
        tb_offset is known.

s390-tod:
        This uses the s390 TOD clock value. This clock is usually in
        sync across virtual machines and STP-enabled machines.

mono:
        This uses the fast monotonic clock (CLOCK_MONOTONIC)
        which is monotonic and is subject to NTP rate adjustments.

mono_raw:
        This is the raw monotonic clock (CLOCK_MONOTONIC_RAW)
        which is monotonic but is not subject to any rate adjustments
        and ticks at the same rate as the hardware clocksource.

boot:
        This is the boot clock (CLOCK_BOOTTIME) and is based on the
        fast monotonic clock, but also accounts for time spent in
        suspend. Since the clock access is designed for use in
        tracing in the suspend path, some side effects are possible
        if clock is accessed after the suspend time is accounted before
        the fast mono clock is updated. In this case, the clock update
        appears to happen slightly sooner than it normally would have.
        Also on 32-bit systems, it's possible that the 64-bit boot offset
        sees a partial update. These effects are rare and post
        processing should be able to handle them. See comments in the
        ktime_get_boot_fast_ns() function for more information.

tai:
        This is the tai clock (CLOCK_TAI) and is derived from the wall-
        clock time. However, this clock does not experience
        discontinuities and backwards jumps caused by NTP inserting leap
        seconds. Since the clock access is designed for use in tracing,
        side effects are possible. The clock access may yield wrong
        readouts in case the internal TAI offset is updated e.g., caused
        by setting the system time or using adjtimex() with an offset.
        These effects are rare and post processing should be able to
        handle them. See comments in the ktime_get_tai_fast_ns()
        function for more information.

To set a clock, simply echo the clock name into this file::

  # echo global > trace_clock

Setting a clock clears the ring buffer content as well as the
"snapshot" buffer.
”h]”(hÌ)”}”(hXj  Whenever an event is recorded into the ring buffer, a
"timestamp" is added. This stamp comes from a specified
clock. By default, ftrace uses the "local" clock. This
clock is very fast and strictly per CPU, but on some
systems it may not be monotonic with respect to other
CPUs. In other words, the local clocks may not be in sync
with local clocks on other CPUs.”h]”hXr  Whenever an event is recorded into the ring buffer, a
â€œtimestampâ€ is added. This stamp comes from a specified
clock. By default, ftrace uses the â€œlocalâ€ clock. This
clock is very fast and strictly per CPU, but on some
systems it may not be monotonic with respect to other
CPUs. In other words, the local clocks may not be in sync
with local clocks on other CPUs.”…””}”(hjU  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjQ  ubhÌ)”}”(hŒUsual clocks for tracing::”h]”hŒUsual clocks for tracing:”…””}”(hjc  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjQ  ubj´  )”}”(hŒ0# cat trace_clock
[local] global counter x86-tsc”h]”hŒ0# cat trace_clock
[local] global counter x86-tsc”…””}”hjq  sbah}”(h]”•Ë     h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MhjQ  ubhÌ)”}”(hŒBThe clock with the square brackets around it is the one in effect.”h]”hŒBThe clock with the square brackets around it is the one in effect.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjQ  ubhŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hŒ9local:
Default clock, but may not be in sync across CPUs
”h]”(hŒterm”“”)”}”(hŒlocal:”h]”hŒlocal:”…””}”(hjš  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhj”  ubhŒ
definition”“”)”}”(hhh]”hÌ)”}”(hŒ1Default clock, but may not be in sync across CPUs”h]”hŒ1Default clock, but may not be in sync across CPUs”…””}”(hj­  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjª  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj”  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mhj  ubj“  )”}”(hŒZglobal:
This clock is in sync with all CPUs but may
be a bit slower than the local clock.
”h]”(j™  )”}”(hŒglobal:”h]”hŒglobal:”…””}”(hjË  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M!hjÇ  ubj©  )”}”(hhh]”hÌ)”}”(hŒQThis clock is in sync with all CPUs but may
be a bit slower than the local clock.”h]”hŒQThis clock is in sync with all CPUs but may
be a bit slower than the local clock.”…””}”(hjÜ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hjÙ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÇ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M!hj  ubj“  )”}”(hŒòcounter:
This is not a clock at all, but literally an atomic
counter. It counts up one by one, but is in sync
with all CPUs. This is useful when you need to
know exactly the order events occurred with respect to
each other on different CPUs.
”h]”(j™  )”}”(hŒcounter:”h]”hŒcounter:”…””}”(hjú  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M(hjö  ubj©  )”}”(hhh]”hÌ)”}”(hŒèThis is not a clock at all, but literally an atomic
counter. It counts up one by one, but is in sync
with all CPUs. This is useful when you need to
know exactly the order events occurred with respect to
each other on different CPUs.”h]”hŒèThis is not a clock at all, but literally an atomic
counter. It counts up one by one, but is in sync
with all CPUs. This is useful when you need to
know exactly the order events occurred with respect to
each other on different CPUs.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M$hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjö  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M(hj  ubj“  )”}”(hŒ`uptime:
This uses the jiffies counter and the time stamp
is relative to the time since boot up.
”h]”(j™  )”}”(hŒuptime:”h]”hŒuptime:”…””}”(hj)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M,hj%  ubj©  )”}”(hhh]”hÌ)”}”(hŒWThis uses the jiffies counter and the time stamp
is relative to the time since boot up.”h]”hŒWThis uses the jiffies counter and the time stamp
is relative to the time since boot up.”…””}”(hj:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M+hj7  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj%  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M,hj  ubj“  )”}”(hŒ perf:
This makes ftrace use the same clock that perf uses.
Eventually perf will be able to read ftrace buffers
and this will help out in interleaving the data.
”h]”(j™  )”}”(hŒperf:”h]”hŒperf:”…””}”(hjX  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M1hjT  ubj©  )”}”(hhh]”hÌ)”}”(hŒ™This makes ftrace use the same clock that perf uses.
Eventually perf will be able to read ftrace buffers
and this will help out in interleaving the data.”h]”hŒ™This makes ftrace use the same clock that perf uses.
Eventually perf will be able to read ftrace buffers
and this will help out in interleaving the data.”…””}”(hji  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M/hjf  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjT  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M1hj  ubj“  )”}”(hŒhx86-tsc:
Architectures may define their own clocks. For
example, x86 uses its own TSC cycle clock here.
”h]”(j™  )”}”(hŒx86-tsc:”h]”hŒx86-tsc:”…””}”(hj‡  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M5hjƒ  ubj©  )”}”(hhh]”hÌ)”}”(hŒ^Architectures may define their own clocks. For
example, x86 uses its own TSC cycle clock here.”h]”hŒ^Architectures may define their own clocks. For
example, x86 uses its own TSC cycle clock here.”…””}”(hj˜  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M4hj•  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjƒ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M5hj  ubj“  )”}”(hŒ«ppc-tb:
This uses the powerpc timebase register value.
This is in sync across CPUs and can also be used
to correlate events across hypervisor/guest if
tb_offset is known.
”h]”(j™  )”}”(hŒppc-tb:”h]”hŒppc-tb:”…””}”(hj¶  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M;hj²  ubj©  )”}”(hhh]”hÌ)”}”(hŒ¢This uses the powerpc timebase register value.
This is in sync across CPUs and can also be used
to correlate events across hypervisor/guest if
tb_offset is known.”h]”hŒ¢This uses the powerpc timebase register value.
This is in sync across CPUs and can also be used
to correlate events across hypervisor/guest if
tb_offset is known.”…””}”(hjÇ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M8hjÄ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj²  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M;hj  ubj“  )”}”(hŒ~s390-tod:
This uses the s390 TOD clock value. This clock is usually in
sync across virtual machines and STP-enabled machines.
”h]”(j™  )”}”(hŒ	s390-tod:”h]”hŒ	s390-tod:”…””}”(hjå  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M?hjá  ubj©  )”}”(hhh]”hÌ)”}”(hŒsThis uses the s390 TOD clock value. This clock is usually in
sync across virtual machines and STP-enabled machines.”h]”hŒsThis uses the s390 TOD clock value. This clock is usually in
sync across virtual machines and STP-enabled machines.”…””}”(hjö  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M>hjó  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjá  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M?hj  ubj“  )”}”(hŒvmono:
This uses the fast monotonic clock (CLOCK_MONOTONIC)
which is monotonic and is subject to NTP rate adjustments.
”h]”(j™  )”}”(hŒmono:”h]”hŒmono:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MChj  ubj©  )”}”(hhh]”hÌ)”}”(hŒoThis uses the fast monotonic clock (CLOCK_MONOTONIC)
which is monotonic and is subject to NTP rate adjustments.”h]”hŒoThis uses the fast monotonic clock (CLOCK_MONOTONIC)
which is monotonic and is subject to NTP rate adjustments.”…””}”(hj%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MBhj"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MChj  ubj“  )”}”(hŒ¶mono_raw:
This is the raw monotonic clock (CLOCK_MONOTONIC_RAW)
which is monotonic but is not subject to any rate adjustments
and ticks at the same rate as the hardware clocksource.
”h]”(j™  )”}”(hŒ	mono_raw:”h]”hŒ	mono_raw:”…””}”(hjC  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MHhj?  ubj©  )”}”(hhh]”hÌ)”}”(hŒ«This is the raw monotonic clock (CLOCK_MONOTONIC_RAW)
which is monotonic but is not subject to any rate adjustments
and ticks at the same rate as the hardware clocksource.”h]”hŒ«This is the raw monotonic clock (CLOCK_MONOTONIC_RAW)
which is monotonic but is not subject to any rate adjustments
and ticks at the same rate as the hardware clocksource.”…””}”(hjT  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MFhjQ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj?  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MHhj  ubj“  )”}”(hXœ  boot:
This is the boot clock (CLOCK_BOOTTIME) and is based on the
fast monotonic clock, but also accounts for time spent in
suspend. Since the clock access is designed for use in
tracing in the suspend path, some side effects are possible
if clock is accessed after the suspend time is accounted before
the fast mono clock is updated. In this case, the clock update
appears to happen slightly sooner than it normally would have.
Also on 32-bit systems, it's possible that the 64-bit boot offset
sees a partial update. These effects are rare and post
processing should be able to handle them. See comments in the
ktime_get_boot_fast_ns() function for more information.
”h]”(j™  )”}”(hŒboot:”h]”hŒboot:”…””}”(hjr  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MUhjn  ubj©  )”}”(hhh]”hÌ)”}”(hX•  This is the boot clock (CLOCK_BOOTTIME) and is based on the
fast monotonic clock, but also accounts for time spent in
suspend. Since the clock access is designed for use in
tracing in the suspend path, some side effects are possible
if clock is accessed after the suspend time is accounted before
the fast mono clock is updated. In this case, the clock update
appears to happen slightly sooner than it normally would have.
Also on 32-bit systems, it's possible that the 64-bit boot offset
sees a partial update. These effects are rare and post
processing should be able to handle them. See comments in the
ktime_get_boot_fast_ns() function for more information.”h]”hX—  This is the boot clock (CLOCK_BOOTTIME) and is based on the
fast monotonic clock, but also accounts for time spent in
suspend. Since the clock access is designed for use in
tracing in the suspend path, some side effects are possible
if clock is accessed after the suspend time is accounted before
the fast mono clock is updated. In this case, the clock update
appears to happen slightly sooner than it normally would have.
Also on 32-bit systems, itâ€™s possible that the 64-bit boot offset
sees a partial update. These effects are rare and post
processing should be able to handle them. See comments in the
ktime_get_boot_fast_ns() function for more information.”…””}”(hjƒ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MKhj€  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjn  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MUhj  ubj“  )”}”(hXK  tai:
This is the tai clock (CLOCK_TAI) and is derived from the wall-
clock time. However, this clock does not experience
discontinuities and backwards jumps caused by NTP inserting leap
seconds. Since the clock access is designed for use in tracing,
side effects are possible. The clock access may yield wrong
readouts in case the internal TAI offset is updated e.g., caused
by setting the system time or using adjtimex() with an offset.
These effects are rare and post processing should be able to
handle them. See comments in the ktime_get_tai_fast_ns()
function for more information.
”h]”(j™  )”}”(hŒtai:”h]”hŒtai:”…””}”(hj¡  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mahj  ubj©  )”}”(hhh]”hÌ)”}”(hXE  This is the tai clock (CLOCK_TAI) and is derived from the wall-
clock time. However, this clock does not experience
discontinuities and backwards jumps caused by NTP inserting leap
seconds. Since the clock access is designed for use in tracing,
side effects are possible. The clock access may yield wrong
readouts in case the internal TAI offset is updated e.g., caused
by setting the system time or using adjtimex() with an offset.
These effects are rare and post processing should be able to
handle them. See comments in the ktime_get_tai_fast_ns()
function for more information.”h]”hXE  This is the tai clock (CLOCK_TAI) and is derived from the wall-
clock time. However, this clock does not experience
discontinuities and backwards jumps caused by NTP inserting leap
seconds. Since the clock access is designed for use in tracing,
side effects are possible. The clock access may yield wrong
readouts in case the internal TAI offset is updated e.g., caused
by setting the system time or using adjtimex() with an offset.
These effects are rare and post processing should be able to
handle them. See comments in the ktime_get_tai_fast_ns()
function for more information.”…””}”(hj²  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MXhj¯  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mahj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjQ  ubhÌ)”}”(hŒ;To set a clock, simply echo the clock name into this file::”h]”hŒ:To set a clock, simply echo the clock name into this file:”…””}”(hjÒ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MchjQ  ubj´  )”}”(hŒ# echo global > trace_clock”h]”hŒ# echo global > trace_clock”…””}”hjà  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MehjQ  ubhÌ)”}”(hŒPSetting a clock clears the ring buffer content as well as the
"snapshot" buffer.”h]”hŒTSetting a clock clears the ring buffer content as well as the
â€œsnapshotâ€ buffer.”…””}”(hjî  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MghjQ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒtrace_marker:”h]”hŒtrace_marker:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mjhj{  ubjh  )”}”(hXñ  This is a very useful file for synchronizing user space
with events happening in the kernel. Writing strings into
this file will be written into the ftrace buffer.

It is useful in applications to open this file at the start
of the application and just reference the file descriptor
for the file::

        void trace_write(const char *fmt, ...)
        {
                va_list ap;
                char buf[256];
                int n;

                if (trace_fd < 0)
                        return;

                va_start(ap, fmt);
                n = vsnprintf(buf, 256, fmt, ap);
                va_end(ap);

                write(trace_fd, buf, n);
        }

start::

        trace_fd = open("trace_marker", O_WRONLY);

Note: Writing into the trace_marker file can also initiate triggers
      that are written into /sys/kernel/tracing/events/ftrace/print/trigger
      See "Event triggers" in Documentation/trace/events.rst and an
      example in Documentation/trace/histogram.rst (Section 3.)
”h]”(hÌ)”}”(hŒ£This is a very useful file for synchronizing user space
with events happening in the kernel. Writing strings into
this file will be written into the ftrace buffer.”h]”hŒ£This is a very useful file for synchronizing user space
with events happening in the kernel. Writing strings into
this file will be written into the ftrace buffer.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mlhj  ubhÌ)”}”(hŒ„It is useful in applications to open this file at the start
of the application and just reference the file descriptor
for the file::”h]”hŒƒIt is useful in applications to open this file at the start
of the application and just reference the file descriptor
for the file:”…””}”(hj"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mphj  ubj´  )”}”(hX  void trace_write(const char *fmt, ...)
{
        va_list ap;
        char buf[256];
        int n;

        if (trace_fd < 0)
                return;

        va_start(ap, fmt);
        n = vsnprintf(buf, 256, fmt, ap);
        va_end(ap);

        write(trace_fd, buf, n);
}”h]”hX  void trace_write(const char *fmt, ...)
{
        va_list ap;
        char buf[256];
        int n;

        if (trace_fd < 0)
                return;

        va_start(ap, fmt);
        n = vsnprintf(buf, 256, fmt, ap);
        va_end(ap);

        write(trace_fd, buf, n);
}”…””}”hj0  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mthj  ubhÌ)”}”(hŒstart::”h]”hŒstart:”…””}”(hj>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M„hj  ubj´  )”}”(hŒ*trace_fd = open("trace_marker", O_WRONLY);”h]”hŒ*trace_fd = open("trace_marker", O_WRONLY);”…””}”hjL  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M†hj  ubjŽ  )”}”(hhh]”j“  )”}”(hX  Note: Writing into the trace_marker file can also initiate triggers
that are written into /sys/kernel/tracing/events/ftrace/print/trigger
See "Event triggers" in Documentation/trace/events.rst and an
example in Documentation/trace/histogram.rst (Section 3.)
”h]”(j™  )”}”(hŒCNote: Writing into the trace_marker file can also initiate triggers”h]”hŒCNote: Writing into the trace_marker file can also initiate triggers”…””}”(hja  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M‹hj]  ubj©  )”}”(hhh]”hÌ)”}”(hŒ½that are written into /sys/kernel/tracing/events/ftrace/print/trigger
See "Event triggers" in Documentation/trace/events.rst and an
example in Documentation/trace/histogram.rst (Section 3.)”h]”hŒÁthat are written into /sys/kernel/tracing/events/ftrace/print/trigger
See â€œEvent triggersâ€ in Documentation/trace/events.rst and an
example in Documentation/trace/histogram.rst (Section 3.)”…””}”(hjr  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‰hjo  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj]  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M‹hjZ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mlhj{  ubhÌ)”}”(hŒtrace_marker_raw:”h]”hŒtrace_marker_raw:”…””}”(hj˜  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hŒ™This is similar to trace_marker above, but is meant for binary data
to be written to it, where a tool can be used to parse the data
from trace_pipe_raw.
”h]”hÌ)”}”(hŒ˜This is similar to trace_marker above, but is meant for binary data
to be written to it, where a tool can be used to parse the data
from trace_pipe_raw.”h]”hŒ˜This is similar to trace_marker above, but is meant for binary data
to be written to it, where a tool can be used to parse the data
from trace_pipe_raw.”…””}”(hjª  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj¦  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒuprobe_events:”h]”hŒuprobe_events:”…””}”(hj¾  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M“hj{  ubjh  )”}”(hŒ:Add dynamic tracepoints in programs.
See uprobetracer.rst
”h]”hÌ)”}”(hŒ9Add dynamic tracepoints in programs.
See uprobetracer.rst”h]”hŒ9Add dynamic tracepoints in programs.
See uprobetracer.rst”…””}”(hjÐ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M•hjÌ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M•hj{  ubhÌ)”}”(hŒuprobe_profile:”h]”hŒuprobe_profile:”…””}”(hjä  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M˜hj{  ubjh  )”}”(hŒ'Uprobe statistics. See uprobetrace.txt
”h]”hÌ)”}”(hŒ&Uprobe statistics. See uprobetrace.txt”h]”hŒ&Uprobe statistics. See uprobetrace.txt”…””}”(hjö  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mšhjò  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mšhj{  ubhÌ)”}”(hŒ
instances:”h]”hŒ
instances:”…””}”(hj
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mœhj{  ubjh  )”}”(hŒ‰This is a way to make multiple trace buffers where different
events can be recorded in different buffers.
See "Instances" section below.
”h]”hÌ)”}”(hŒˆThis is a way to make multiple trace buffers where different
events can be recorded in different buffers.
See "Instances" section below.”h]”hŒŒThis is a way to make multiple trace buffers where different
events can be recorded in different buffers.
See â€œInstancesâ€ section below.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mžhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mžhj{  ubhÌ)”}”(hŒevents:”h]”hŒevents:”…””}”(hj0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¢hj{  ubjh  )”}”(hXd  This is the trace event directory. It holds event tracepoints
(also known as static tracepoints) that have been compiled
into the kernel. It shows what event tracepoints exist
and how they are grouped by system. There are "enable"
files at various levels that can enable the tracepoints
when a "1" is written to them.

See events.rst for more information.
”h]”(hÌ)”}”(hX=  This is the trace event directory. It holds event tracepoints
(also known as static tracepoints) that have been compiled
into the kernel. It shows what event tracepoints exist
and how they are grouped by system. There are "enable"
files at various levels that can enable the tracepoints
when a "1" is written to them.”h]”hXE  This is the trace event directory. It holds event tracepoints
(also known as static tracepoints) that have been compiled
into the kernel. It shows what event tracepoints exist
and how they are grouped by system. There are â€œenableâ€
files at various levels that can enable the tracepoints
when a â€œ1â€ is written to them.”…””}”(hjB  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¤hj>  ubhÌ)”}”(hŒ$See events.rst for more information.”h]”hŒ$See events.rst for more information.”…””}”(hjP  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M«hj>  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M¤hj{  ubhÌ)”}”(hŒ
set_event:”h]”hŒ
set_event:”…””}”(hjd  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M­hj{  ubjh  )”}”(hŒfBy echoing in the event into this file, will enable that event.

See events.rst for more information.
”h]”(hÌ)”}”(hŒ?By echoing in the event into this file, will enable that event.”h]”hŒ?By echoing in the event into this file, will enable that event.”…””}”(hjv  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¯hjr  ubhÌ)”}”(hŒ$See events.rst for more information.”h]”hŒ$See events.rst for more information.”…””}”(hj„  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M±hjr  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M¯hj{  ubhÌ)”}”(hŒshow_event_filters:”h]”hŒshow_event_filters:”…””}”(hj˜  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M³hj{  ubjh  )”}”(hŒ A list of events that have filters. This shows the
system/event pair along with the filter that is attached to
the event.

See events.rst for more information.
”h]”(hÌ)”}”(hŒyA list of events that have filters. This shows the
system/event pair along with the filter that is attached to
the event.”h]”hŒyA list of events that have filters. This shows the
system/event pair along with the filter that is attached to
the event.”…””}”(hjª  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mµhj¦  ubhÌ)”}”(hŒ$See events.rst for more information.”h]”hŒ$See events.rst for more information.”…””}”(hj¸  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¹hj¦  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mµhj{  ubhÌ)”}”(hŒshow_event_triggers:”h]”hŒshow_event_triggers:”…””}”(hjÌ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M»hj{  ubjh  )”}”(hŒ¢A list of events that have triggers. This shows the
system/event pair along with the trigger that is attached to
the event.

See events.rst for more information.
”h]”(hÌ)”}”(hŒ{A list of events that have triggers. This shows the
system/event pair along with the trigger that is attached to
the event.”h]”hŒ{A list of events that have triggers. This shows the
system/event pair along with the trigger that is attached to
the event.”…””}”(hjÞ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M½hjÚ  ubhÌ)”}”(hŒ$See events.rst for more information.”h]”hŒ$See events.rst for more information.”…””}”(hjì  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÁhjÚ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M½hj{  ubhÌ)”}”(hŒavailable_events:”h]”hŒavailable_events:”…””}”(hj   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÃhj{  ubjh  )”}”(hŒWA list of events that can be enabled in tracing.

See events.rst for more information.
”h]”(hÌ)”}”(hŒ0A list of events that can be enabled in tracing.”h]”hŒ0A list of events that can be enabled in tracing.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÅhj  ubhÌ)”}”(hŒ$See events.rst for more information.”h]”hŒ$See events.rst for more information.”…””}”(hj   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÇhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÅhj{  ubhÌ)”}”(hŒtimestamp_mode:”h]”hŒtimestamp_mode:”…””}”(hj4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÉhj{  ubjh  )”}”(hXÌ  Certain tracers may change the timestamp mode used when
logging trace events into the event buffer.  Events with
different modes can coexist within a buffer but the mode in
effect when an event is logged determines which timestamp mode
is used for that event.  The default timestamp mode is
'delta'.

Usual timestamp modes for tracing:

  # cat timestamp_mode
  [delta] absolute

  The timestamp mode with the square brackets around it is the
  one in effect.

  delta: Default timestamp mode - timestamp is a delta against
         a per-buffer timestamp.

  absolute: The timestamp is a full timestamp, not a delta
         against some other value.  As such it takes up more
         space and is less efficient.
”h]”(hÌ)”}”(hX+  Certain tracers may change the timestamp mode used when
logging trace events into the event buffer.  Events with
different modes can coexist within a buffer but the mode in
effect when an event is logged determines which timestamp mode
is used for that event.  The default timestamp mode is
'delta'.”h]”hX/  Certain tracers may change the timestamp mode used when
logging trace events into the event buffer.  Events with
different modes can coexist within a buffer but the mode in
effect when an event is logged determines which timestamp mode
is used for that event.  The default timestamp mode is
â€˜deltaâ€™.”…””}”(hjF  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MËhjB  ubhÌ)”}”(hŒ"Usual timestamp modes for tracing:”h]”hŒ"Usual timestamp modes for tracing:”…””}”(hjT  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÒhjB  ubjh  )”}”(hXi  # cat timestamp_mode
[delta] absolute

The timestamp mode with the square brackets around it is the
one in effect.

delta: Default timestamp mode - timestamp is a delta against
       a per-buffer timestamp.

absolute: The timestamp is a full timestamp, not a delta
       against some other value.  As such it takes up more
       space and is less efficient.
”h]”(hÌ)”}”(hŒ%# cat timestamp_mode
[delta] absolute”h]”hŒ%# cat timestamp_mode
[delta] absolute”…””}”(hjf  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÔhjb  ubhÌ)”}”(hŒKThe timestamp mode with the square brackets around it is the
one in effect.”h]”hŒKThe timestamp mode with the square brackets around it is the
one in effect.”…””}”(hjt  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M×hjb  ubjŽ  )”}”(hhh]”(j“  )”}”(hŒUdelta: Default timestamp mode - timestamp is a delta against
a per-buffer timestamp.
”h]”(j™  )”}”(hŒ<delta: Default timestamp mode - timestamp is a delta against”h]”hŒ<delta: Default timestamp mode - timestamp is a delta against”…””}”(hj‰  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÛhj…  ubj©  )”}”(hhh]”hÌ)”}”(hŒa per-buffer timestamp.”h]”hŒa per-buffer timestamp.”…””}”(hjš  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÛhj—  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj…  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÛhj‚  ubj“  )”}”(hŒŠabsolute: The timestamp is a full timestamp, not a delta
against some other value.  As such it takes up more
space and is less efficient.
”h]”(j™  )”}”(hŒ8absolute: The timestamp is a full timestamp, not a delta”h]”hŒ8absolute: The timestamp is a full timestamp, not a delta”…””}”(hj¸  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mßhj´  ubj©  )”}”(hhh]”hÌ)”}”(hŒPagainst some other value.  As such it takes up more
space and is less efficient.”h]”hŒPagainst some other value.  As such it takes up more
space and is less efficient.”…””}”(hjÉ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÞhjÆ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj´  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mßhj‚  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjb  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÔhjB  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MËhj{  ubhÌ)”}”(hŒhwlat_detector:”h]”hŒhwlat_detector:”…””}”(hjõ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Máhj{  ubjh  )”}”(hŒ\Directory for the Hardware Latency Detector.
See "Hardware Latency Detector" section below.
”h]”hÌ)”}”(hŒ[Directory for the Hardware Latency Detector.
See "Hardware Latency Detector" section below.”h]”hŒ_Directory for the Hardware Latency Detector.
See â€œHardware Latency Detectorâ€ section below.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mãhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mãhj{  ubhÌ)”}”(hŒper_cpu:”h]”hŒper_cpu:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mæhj{  ubjh  )”}”(hŒAThis is a directory that contains the trace per_cpu information.
”h]”hÌ)”}”(hŒ@This is a directory that contains the trace per_cpu information.”h]”hŒ@This is a directory that contains the trace per_cpu information.”…””}”(hj-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mèhj)  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mèhj{  ubhÌ)”}”(hŒper_cpu/cpu0/buffer_size_kb:”h]”hŒper_cpu/cpu0/buffer_size_kb:”…””}”(hjA  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mêhj{  ubjh  )”}”(hXK  The ftrace buffer is defined per_cpu. That is, there's a separate
buffer for each CPU to allow writes to be done atomically,
and free from cache bouncing. These buffers may have different
size buffers. This file is similar to the buffer_size_kb
file, but it only displays or sets the buffer size for the
specific CPU. (here cpu0).
”h]”hÌ)”}”(hXJ  The ftrace buffer is defined per_cpu. That is, there's a separate
buffer for each CPU to allow writes to be done atomically,
and free from cache bouncing. These buffers may have different
size buffers. This file is similar to the buffer_size_kb
file, but it only displays or sets the buffer size for the
specific CPU. (here cpu0).”h]”hXL  The ftrace buffer is defined per_cpu. That is, thereâ€™s a separate
buffer for each CPU to allow writes to be done atomically,
and free from cache bouncing. These buffers may have different
size buffers. This file is similar to the buffer_size_kb
file, but it only displays or sets the buffer size for the
specific CPU. (here cpu0).”…””}”(hjS  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MìhjO  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mìhj{  ubhÌ)”}”(hŒper_cpu/cpu0/trace:”h]”hŒper_cpu/cpu0/trace:”…””}”(hjg  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Móhj{  ubjh  )”}”(hŒ”This is similar to the "trace" file, but it will only display
the data specific for the CPU. If written to, it only clears
the specific CPU buffer.
”h]”hÌ)”}”(hŒ“This is similar to the "trace" file, but it will only display
the data specific for the CPU. If written to, it only clears
the specific CPU buffer.”h]”hŒ—This is similar to the â€œtraceâ€ file, but it will only display
the data specific for the CPU. If written to, it only clears
the specific CPU buffer.”…””}”(hjy  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mõhju  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mõhj{  ubhÌ)”}”(hŒper_cpu/cpu0/trace_pipe”h]”hŒper_cpu/cpu0/trace_pipe”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mùhj{  ubjh  )”}”(hŒ‰This is similar to the "trace_pipe" file, and is a consuming
read, but it will only display (and consume) the data specific
for the CPU.
”h]”hÌ)”}”(hŒˆThis is similar to the "trace_pipe" file, and is a consuming
read, but it will only display (and consume) the data specific
for the CPU.”h]”hŒŒThis is similar to the â€œtrace_pipeâ€ file, and is a consuming
read, but it will only display (and consume) the data specific
for the CPU.”…””}”(hjŸ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mûhj›  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mûhj{  ubhÌ)”}”(hŒper_cpu/cpu0/trace_pipe_raw”h]”hŒper_cpu/cpu0/trace_pipe_raw”…””}”(hj³  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mÿhj{  ubjh  )”}”(hX•  For tools that can parse the ftrace ring buffer binary format,
the trace_pipe_raw file can be used to extract the data
from the ring buffer directly. With the use of the splice()
system call, the buffer data can be quickly transferred to
a file or to the network where a server is collecting the
data.

Like trace_pipe, this is a consuming reader, where multiple
reads will always produce different data.
”h]”(hÌ)”}”(hX-  For tools that can parse the ftrace ring buffer binary format,
the trace_pipe_raw file can be used to extract the data
from the ring buffer directly. With the use of the splice()
system call, the buffer data can be quickly transferred to
a file or to the network where a server is collecting the
data.”h]”hX-  For tools that can parse the ftrace ring buffer binary format,
the trace_pipe_raw file can be used to extract the data
from the ring buffer directly. With the use of the splice()
system call, the buffer data can be quickly transferred to
a file or to the network where a server is collecting the
data.”…””}”(hjÅ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjÁ  ubhÌ)”}”(hŒeLike trace_pipe, this is a consuming reader, where multiple
reads will always produce different data.”h]”hŒeLike trace_pipe, this is a consuming reader, where multiple
reads will always produce different data.”…””}”(hjÓ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjÁ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒper_cpu/cpu0/snapshot:”h]”hŒper_cpu/cpu0/snapshot:”…””}”(hjç  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hŒÒThis is similar to the main "snapshot" file, but will only
snapshot the current CPU (if supported). It only displays
the content of the snapshot for a given CPU, and if
written to, only clears this CPU buffer.
”h]”hÌ)”}”(hŒÑThis is similar to the main "snapshot" file, but will only
snapshot the current CPU (if supported). It only displays
the content of the snapshot for a given CPU, and if
written to, only clears this CPU buffer.”h]”hŒÕThis is similar to the main â€œsnapshotâ€ file, but will only
snapshot the current CPU (if supported). It only displays
the content of the snapshot for a given CPU, and if
written to, only clears this CPU buffer.”…””}”(hjù  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjõ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒper_cpu/cpu0/snapshot_raw:”h]”hŒper_cpu/cpu0/snapshot_raw:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hŒkSimilar to the trace_pipe_raw, but will read the binary format
from the snapshot buffer for the given CPU.
”h]”hÌ)”}”(hŒjSimilar to the trace_pipe_raw, but will read the binary format
from the snapshot buffer for the given CPU.”h]”hŒjSimilar to the trace_pipe_raw, but will read the binary format
from the snapshot buffer for the given CPU.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubhÌ)”}”(hŒper_cpu/cpu0/stats:”h]”hŒper_cpu/cpu0/stats:”…””}”(hj3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{  ubjh  )”}”(hXÆ  This displays certain stats about the ring buffer:

entries:
        The number of events that are still in the buffer.

overrun:
        The number of lost events due to overwriting when
        the buffer was full.

commit overrun:
        Should always be zero.
        This gets set if so many events happened within a nested
        event (ring buffer is re-entrant), that it fills the
        buffer and starts dropping events.

bytes:
        Bytes actually read (not overwritten).

oldest event ts:
        The oldest timestamp in the buffer

now ts:
        The current timestamp

dropped events:
        Events lost due to overwrite option being off.

read events:
        The number of events read.
”h]”(hÌ)”}”(hŒ2This displays certain stats about the ring buffer:”h]”hŒ2This displays certain stats about the ring buffer:”…””}”(hjE  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjA  ubjŽ  )”}”(hhh]”(j“  )”}”(hŒ<entries:
The number of events that are still in the buffer.
”h]”(j™  )”}”(hŒentries:”h]”hŒentries:”…””}”(hjZ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MhjV  ubj©  )”}”(hhh]”hÌ)”}”(hŒ2The number of events that are still in the buffer.”h]”hŒ2The number of events that are still in the buffer.”…””}”(hjk  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjh  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjV  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MhjS  ubj“  )”}”(hŒPoverrun:
The number of lost events due to overwriting when
the buffer was full.
”h]”(j™  )”}”(hŒoverrun:”h]”hŒoverrun:”…””}”(hj‰  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M hj…  ubj©  )”}”(hhh]”hÌ)”}”(hŒFThe number of lost events due to overwriting when
the buffer was full.”h]”hŒFThe number of lost events due to overwriting when
the buffer was full.”…””}”(hjš  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj—  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj…  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M hjS  ubj“  )”}”(hŒ¸commit overrun:
Should always be zero.
This gets set if so many events happened within a nested
event (ring buffer is re-entrant), that it fills the
buffer and starts dropping events.
”h]”(j™  )”}”(hŒcommit overrun:”h]”hŒcommit overrun:”…””}”(hj¸  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M&hj´  ubj©  )”}”(hhh]”hÌ)”}”(hŒ§Should always be zero.
This gets set if so many events happened within a nested
event (ring buffer is re-entrant), that it fills the
buffer and starts dropping events.”h]”hŒ§Should always be zero.
This gets set if so many events happened within a nested
event (ring buffer is re-entrant), that it fills the
buffer and starts dropping events.”…””}”(hjÉ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M#hjÆ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj´  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M&hjS  ubj“  )”}”(hŒ.bytes:
Bytes actually read (not overwritten).
”h]”(j™  )”}”(hŒbytes:”h]”hŒbytes:”…””}”(hjç  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M)hjã  ubj©  )”}”(hhh]”hÌ)”}”(hŒ&Bytes actually read (not overwritten).”h]”hŒ&Bytes actually read (not overwritten).”…””}”(hjø  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M)hjõ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjã  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M)hjS  ubj“  )”}”(hŒ4oldest event ts:
The oldest timestamp in the buffer
”h]”(j™  )”}”(hŒoldest event ts:”h]”hŒoldest event ts:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M,hj  ubj©  )”}”(hhh]”hÌ)”}”(hŒ"The oldest timestamp in the buffer”h]”hŒ"The oldest timestamp in the buffer”…””}”(hj'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M,hj$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M,hjS  ubj“  )”}”(hŒnow ts:
The current timestamp
”h]”(j™  )”}”(hŒnow ts:”h]”hŒnow ts:”…””}”(hjE  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M/hjA  ubj©  )”}”(hhh]”hÌ)”}”(hŒThe current timestamp”h]”hŒThe current timestamp”…””}”(hjV  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M/hjS  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjA  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M/hjS  ubj“  )”}”(hŒ?dropped events:
Events lost due to overwrite option being off.
”h]”(j™  )”}”(hŒdropped events:”h]”hŒdropped events:”…””}”(hjt  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M2hjp  ubj©  )”}”(hhh]”hÌ)”}”(hŒ.Events lost due to overwrite option being off.”h]”hŒ.Events lost due to overwrite option being off.”…””}”(hj…  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M2hj‚  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjp  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M2hjS  ubj“  )”}”(hŒ(read events:
The number of events read.
”h]”(j™  )”}”(hŒread events:”h]”hŒread events:”…””}”(hj£  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M5hjŸ  ubj©  )”}”(hhh]”hÌ)”}”(hŒThe number of events read.”h]”hŒThe number of events read.”…””}”(hj´  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M5hj±  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjŸ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M5hjS  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjA  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj{  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´K_hji  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´K]hj†  h²hubeh}”(h]”Œthe-file-system”ah ]”h"]”Œthe file system”ah$]”h&]”uh1hµhh·h²hh³hÊh´K/ubh¶)”}”(hhh]”(h»)”}”(hŒThe Tracers”h]”hŒThe Tracers”…””}”(hjñ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjî  h²hh³hÊh´M8ubhÌ)”}”(hŒ;Here is the list of current tracers that may be configured.”h]”hŒ;Here is the list of current tracers that may be configured.”…””}”(hjÿ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M:hjî  h²hubjh  )”}”(hX×
  "function"

      Function call tracer to trace all kernel functions.

"function_graph"

      Similar to the function tracer except that the
      function tracer probes the functions on their entry
      whereas the function graph tracer traces on both entry
      and exit of the functions. It then provides the ability
      to draw a graph of function calls similar to C code
      source.

      Note that the function graph calculates the timings of when the
      function starts and returns internally and for each instance. If
      there are two instances that run function graph tracer and traces
      the same functions, the length of the timings may be slightly off as
      each read the timestamp separately and not at the same time.

"blk"

      The block tracer. The tracer used by the blktrace user
      application.

"hwlat"

      The Hardware Latency tracer is used to detect if the hardware
      produces any latency. See "Hardware Latency Detector" section
      below.

"irqsoff"

      Traces the areas that disable interrupts and saves
      the trace with the longest max latency.
      See tracing_max_latency. When a new max is recorded,
      it replaces the old trace. It is best to view this
      trace with the latency-format option enabled, which
      happens automatically when the tracer is selected.

"preemptoff"

      Similar to irqsoff but traces and records the amount of
      time for which preemption is disabled.

"preemptirqsoff"

      Similar to irqsoff and preemptoff, but traces and
      records the largest time for which irqs and/or preemption
      is disabled.

"wakeup"

      Traces and records the max latency that it takes for
      the highest priority task to get scheduled after
      it has been woken up.
      Traces all tasks as an average developer would expect.

"wakeup_rt"

      Traces and records the max latency that it takes for just
      RT tasks (as the current "wakeup" does). This is useful
      for those interested in wake up timings of RT tasks.

"wakeup_dl"

      Traces and records the max latency that it takes for
      a SCHED_DEADLINE task to be woken (as the "wakeup" and
      "wakeup_rt" does).

"mmiotrace"

      A special tracer that is used to trace binary modules.
      It will trace all the calls that a module makes to the
      hardware. Everything it writes and reads from the I/O
      as well.

"branch"

      This tracer can be configured when tracing likely/unlikely
      calls within the kernel. It will trace when a likely and
      unlikely branch is hit and if it was correct in its prediction
      of being correct.

"nop"

      This is the "trace nothing" tracer. To remove all
      tracers from tracing simply echo "nop" into
      current_tracer.
”h]”(hÌ)”}”(hŒ
"function"”h]”hŒâ€œfunctionâ€”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M<hj  ubjh  )”}”(hŒ4Function call tracer to trace all kernel functions.
”h]”hÌ)”}”(hŒ3Function call tracer to trace all kernel functions.”h]”hŒ3Function call tracer to trace all kernel functions.”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M>hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M>hj  ubhÌ)”}”(hŒ"function_graph"”h]”hŒâ€œfunction_graphâ€”…””}”(hj7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M@hj  ubjh  )”}”(hXT  Similar to the function tracer except that the
function tracer probes the functions on their entry
whereas the function graph tracer traces on both entry
and exit of the functions. It then provides the ability
to draw a graph of function calls similar to C code
source.

Note that the function graph calculates the timings of when the
function starts and returns internally and for each instance. If
there are two instances that run function graph tracer and traces
the same functions, the length of the timings may be slightly off as
each read the timestamp separately and not at the same time.
”h]”(hÌ)”}”(hX  Similar to the function tracer except that the
function tracer probes the functions on their entry
whereas the function graph tracer traces on both entry
and exit of the functions. It then provides the ability
to draw a graph of function calls similar to C code
source.”h]”hX  Similar to the function tracer except that the
function tracer probes the functions on their entry
whereas the function graph tracer traces on both entry
and exit of the functions. It then provides the ability
to draw a graph of function calls similar to C code
source.”…””}”(hjI  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MBhjE  ubhÌ)”}”(hXD  Note that the function graph calculates the timings of when the
function starts and returns internally and for each instance. If
there are two instances that run function graph tracer and traces
the same functions, the length of the timings may be slightly off as
each read the timestamp separately and not at the same time.”h]”hXD  Note that the function graph calculates the timings of when the
function starts and returns internally and for each instance. If
there are two instances that run function graph tracer and traces
the same functions, the length of the timings may be slightly off as
each read the timestamp separately and not at the same time.”…””}”(hjW  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MIhjE  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MBhj  ubhÌ)”}”(hŒ"blk"”h]”hŒ	â€œblkâ€”…””}”(hjk  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MOhj  ubjh  )”}”(hŒDThe block tracer. The tracer used by the blktrace user
application.
”h]”hÌ)”}”(hŒCThe block tracer. The tracer used by the blktrace user
application.”h]”hŒCThe block tracer. The tracer used by the blktrace user
application.”…””}”(hj}  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MQhjy  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MQhj  ubhÌ)”}”(hŒ"hwlat"”h]”hŒâ€œhwlatâ€”…””}”(hj‘  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MThj  ubjh  )”}”(hŒƒThe Hardware Latency tracer is used to detect if the hardware
produces any latency. See "Hardware Latency Detector" section
below.
”h]”hÌ)”}”(hŒ‚The Hardware Latency tracer is used to detect if the hardware
produces any latency. See "Hardware Latency Detector" section
below.”h]”hŒ†The Hardware Latency tracer is used to detect if the hardware
produces any latency. See â€œHardware Latency Detectorâ€ section
below.”…””}”(hj£  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MVhjŸ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MVhj  ubhÌ)”}”(hŒ	"irqsoff"”h]”hŒâ€œirqsoffâ€”…””}”(hj·  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MZhj  ubjh  )”}”(hX*  Traces the areas that disable interrupts and saves
the trace with the longest max latency.
See tracing_max_latency. When a new max is recorded,
it replaces the old trace. It is best to view this
trace with the latency-format option enabled, which
happens automatically when the tracer is selected.
”h]”hÌ)”}”(hX)  Traces the areas that disable interrupts and saves
the trace with the longest max latency.
See tracing_max_latency. When a new max is recorded,
it replaces the old trace. It is best to view this
trace with the latency-format option enabled, which
happens automatically when the tracer is selected.”h]”hX)  Traces the areas that disable interrupts and saves
the trace with the longest max latency.
See tracing_max_latency. When a new max is recorded,
it replaces the old trace. It is best to view this
trace with the latency-format option enabled, which
happens automatically when the tracer is selected.”…””}”(hjÉ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M\hjÅ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M\hj  ubhÌ)”}”(hŒ"preemptoff"”h]”hŒâ€œpreemptoffâ€”…””}”(hjÝ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mchj  ubjh  )”}”(hŒ_Similar to irqsoff but traces and records the amount of
time for which preemption is disabled.
”h]”hÌ)”}”(hŒ^Similar to irqsoff but traces and records the amount of
time for which preemption is disabled.”h]”hŒ^Similar to irqsoff but traces and records the amount of
time for which preemption is disabled.”…””}”(hjï  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mehjë  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mehj  ubhÌ)”}”(hŒ"preemptirqsoff"”h]”hŒâ€œpreemptirqsoffâ€”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhhj  ubjh  )”}”(hŒySimilar to irqsoff and preemptoff, but traces and
records the largest time for which irqs and/or preemption
is disabled.
”h]”hÌ)”}”(hŒxSimilar to irqsoff and preemptoff, but traces and
records the largest time for which irqs and/or preemption
is disabled.”h]”hŒxSimilar to irqsoff and preemptoff, but traces and
records the largest time for which irqs and/or preemption
is disabled.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mjhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mjhj  ubhÌ)”}”(hŒ"wakeup"”h]”hŒâ€œwakeupâ€”…””}”(hj)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mnhj  ubjh  )”}”(hŒ³Traces and records the max latency that it takes for
the highest priority task to get scheduled after
it has been woken up.
Traces all tasks as an average developer would expect.
”h]”hÌ)”}”(hŒ²Traces and records the max latency that it takes for
the highest priority task to get scheduled after
it has been woken up.
Traces all tasks as an average developer would expect.”h]”hŒ²Traces and records the max latency that it takes for
the highest priority task to get scheduled after
it has been woken up.
Traces all tasks as an average developer would expect.”…””}”(hj;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mphj7  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mphj  ubhÌ)”}”(hŒ"wakeup_rt"”h]”hŒâ€œwakeup_rtâ€”…””}”(hjO  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Muhj  ubjh  )”}”(hŒ§Traces and records the max latency that it takes for just
RT tasks (as the current "wakeup" does). This is useful
for those interested in wake up timings of RT tasks.
”h]”hÌ)”}”(hŒ¦Traces and records the max latency that it takes for just
RT tasks (as the current "wakeup" does). This is useful
for those interested in wake up timings of RT tasks.”h]”hŒªTraces and records the max latency that it takes for just
RT tasks (as the current â€œwakeupâ€ does). This is useful
for those interested in wake up timings of RT tasks.”…””}”(hja  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mwhj]  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mwhj  ubhÌ)”}”(hŒ"wakeup_dl"”h]”hŒâ€œwakeup_dlâ€”…””}”(hju  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M{hj  ubjh  )”}”(hŒTraces and records the max latency that it takes for
a SCHED_DEADLINE task to be woken (as the "wakeup" and
"wakeup_rt" does).
”h]”hÌ)”}”(hŒ~Traces and records the max latency that it takes for
a SCHED_DEADLINE task to be woken (as the "wakeup" and
"wakeup_rt" does).”h]”hŒ†Traces and records the max latency that it takes for
a SCHED_DEADLINE task to be woken (as the â€œwakeupâ€ and
â€œwakeup_rtâ€ does).”…””}”(hj‡  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M}hjƒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M}hj  ubhÌ)”}”(hŒ"mmiotrace"”h]”hŒâ€œmmiotraceâ€”…””}”(hj›  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj  ubjh  )”}”(hŒ­A special tracer that is used to trace binary modules.
It will trace all the calls that a module makes to the
hardware. Everything it writes and reads from the I/O
as well.
”h]”hÌ)”}”(hŒ¬A special tracer that is used to trace binary modules.
It will trace all the calls that a module makes to the
hardware. Everything it writes and reads from the I/O
as well.”h]”hŒ¬A special tracer that is used to trace binary modules.
It will trace all the calls that a module makes to the
hardware. Everything it writes and reads from the I/O
as well.”…””}”(hj­  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mƒhj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mƒhj  ubhÌ)”}”(hŒ"branch"”h]”hŒâ€œbranchâ€”…””}”(hjÁ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mˆhj  ubjh  )”}”(hŒÅThis tracer can be configured when tracing likely/unlikely
calls within the kernel. It will trace when a likely and
unlikely branch is hit and if it was correct in its prediction
of being correct.
”h]”hÌ)”}”(hŒÄThis tracer can be configured when tracing likely/unlikely
calls within the kernel. It will trace when a likely and
unlikely branch is hit and if it was correct in its prediction
of being correct.”h]”hŒÄThis tracer can be configured when tracing likely/unlikely
calls within the kernel. It will trace when a likely and
unlikely branch is hit and if it was correct in its prediction
of being correct.”…””}”(hjÓ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŠhjÏ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MŠhj  ubhÌ)”}”(hŒ"nop"”h]”hŒ	â€œnopâ€”…””}”(hjç  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj  ubjh  )”}”(hŒnThis is the "trace nothing" tracer. To remove all
tracers from tracing simply echo "nop" into
current_tracer.
”h]”hÌ)”}”(hŒmThis is the "trace nothing" tracer. To remove all
tracers from tracing simply echo "nop" into
current_tracer.”h]”hŒuThis is the â€œtrace nothingâ€ tracer. To remove all
tracers from tracing simply echo â€œnopâ€ into
current_tracer.”…””}”(hjù  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‘hjõ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M‘hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M<hjî  h²hubeh}”(h]”Œthe-tracers”ah ]”h"]”Œthe tracers”ah$]”h&]”uh1hµhh·h²hh³hÊh´M8ubh¶)”}”(hhh]”(h»)”}”(hŒError conditions”h]”hŒError conditions”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj  h²hh³hÊh´M–ubjh  )”}”(hX  For most ftrace commands, failure modes are obvious and communicated
using standard return codes.

For other more involved commands, extended error information may be
available via the tracing/error_log file.  For the commands that
support it, reading the tracing/error_log file after an error will
display more detailed information about what went wrong, if
information is available.  The tracing/error_log file is a circular
error log displaying a small number (currently, 8) of ftrace errors
for the last (8) failed commands.

The extended error information and usage takes the form shown in
this example::

  # echo xxx > /sys/kernel/tracing/events/sched/sched_wakeup/trigger
  echo: write error: Invalid argument

  # cat /sys/kernel/tracing/error_log
  [ 5348.887237] location: error: Couldn't yyy: zzz
    Command: xxx
             ^
  [ 7517.023364] location: error: Bad rrr: sss
    Command: ppp qqq
                 ^

To clear the error log, echo the empty string into it::

  # echo > /sys/kernel/tracing/error_log
”h]”(hÌ)”}”(hŒaFor most ftrace commands, failure modes are obvious and communicated
using standard return codes.”h]”hŒaFor most ftrace commands, failure modes are obvious and communicated
using standard return codes.”…””}”(hj0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M˜hj,  ubhÌ)”}”(hX­  For other more involved commands, extended error information may be
available via the tracing/error_log file.  For the commands that
support it, reading the tracing/error_log file after an error will
display more detailed information about what went wrong, if
information is available.  The tracing/error_log file is a circular
error log displaying a small number (currently, 8) of ftrace errors
for the last (8) failed commands.”h]”hX­  For other more involved commands, extended error information may be
available via the tracing/error_log file.  For the commands that
support it, reading the tracing/error_log file after an error will
display more detailed information about what went wrong, if
information is available.  The tracing/error_log file is a circular
error log displaying a small number (currently, 8) of ftrace errors
for the last (8) failed commands.”…””}”(hj>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M›hj,  ubhÌ)”}”(hŒOThe extended error information and usage takes the form shown in
this example::”h]”hŒNThe extended error information and usage takes the form shown in
this example:”…””}”(hjL  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M£hj,  ubj´  )”}”(hX*  # echo xxx > /sys/kernel/tracing/events/sched/sched_wakeup/trigger
echo: write error: Invalid argument

# cat /sys/kernel/tracing/error_log
[ 5348.887237] location: error: Couldn't yyy: zzz
  Command: xxx
           ^
[ 7517.023364] location: error: Bad rrr: sss
  Command: ppp qqq
               ^”h]”hX*  # echo xxx > /sys/kernel/tracing/events/sched/sched_wakeup/trigger
echo: write error: Invalid argument

# cat /sys/kernel/tracing/error_log
[ 5348.887237] location: error: Couldn't yyy: zzz
  Command: xxx
           ^
[ 7517.023364] location: error: Bad rrr: sss
  Command: ppp qqq
               ^”…””}”hjZ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¦hj,  ubhÌ)”}”(hŒ7To clear the error log, echo the empty string into it::”h]”hŒ6To clear the error log, echo the empty string into it:”…””}”(hjh  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M±hj,  ubj´  )”}”(hŒ&# echo > /sys/kernel/tracing/error_log”h]”hŒ&# echo > /sys/kernel/tracing/error_log”…””}”hjv  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M³hj,  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M˜hj  h²hubeh}”(h]”Œerror-conditions”ah ]”h"]”Œerror conditions”ah$]”h&]”uh1hµhh·h²hh³hÊh´M–ubh¶)”}”(hhh]”(h»)”}”(hŒExamples of using the tracer”h]”hŒExamples of using the tracer”…””}”(hj•  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj’  h²hh³hÊh´M¶ubhÌ)”}”(hŒHere are typical examples of using the tracers when controlling
them only with the tracefs interface (without using any
user-land utilities).”h]”hŒHere are typical examples of using the tracers when controlling
them only with the tracefs interface (without using any
user-land utilities).”…””}”(hj£  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¸hj’  h²hubeh}”(h]”Œexamples-of-using-the-tracer”ah ]”h"]”Œexamples of using the tracer”ah$]”h&]”uh1hµhh·h²hh³hÊh´M¶ubh¶)”}”(hhh]”(h»)”}”(hŒOutput format:”h]”hŒOutput format:”…””}”(hj¼  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj¹  h²hh³hÊh´M½ubhÌ)”}”(hŒ=Here is an example of the output format of the file "trace"::”h]”hŒ@Here is an example of the output format of the file â€œtraceâ€:”…””}”(hjÊ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¿hj¹  h²hubj´  )”}”(hXÜ  # tracer: function
#
# entries-in-buffer/entries-written: 140080/250280   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1977  [000] .... 17284.993652: sys_close <-system_call_fastpath
            bash-1977  [000] .... 17284.993653: __close_fd <-sys_close
            bash-1977  [000] .... 17284.993653: _raw_spin_lock <-__close_fd
            sshd-1974  [003] .... 17284.993653: __srcu_read_unlock <-fsnotify
            bash-1977  [000] .... 17284.993654: add_preempt_count <-_raw_spin_lock
            bash-1977  [000] ...1 17284.993655: _raw_spin_unlock <-__close_fd
            bash-1977  [000] ...1 17284.993656: sub_preempt_count <-_raw_spin_unlock
            bash-1977  [000] .... 17284.993657: filp_close <-__close_fd
            bash-1977  [000] .... 17284.993657: dnotify_flush <-filp_close
            sshd-1974  [003] .... 17284.993658: sys_select <-system_call_fastpath
            ....”h]”hXÜ  # tracer: function
#
# entries-in-buffer/entries-written: 140080/250280   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1977  [000] .... 17284.993652: sys_close <-system_call_fastpath
            bash-1977  [000] .... 17284.993653: __close_fd <-sys_close
            bash-1977  [000] .... 17284.993653: _raw_spin_lock <-__close_fd
            sshd-1974  [003] .... 17284.993653: __srcu_read_unlock <-fsnotify
            bash-1977  [000] .... 17284.993654: add_preempt_count <-_raw_spin_lock
            bash-1977  [000] ...1 17284.993655: _raw_spin_unlock <-__close_fd
            bash-1977  [000] ...1 17284.993656: sub_preempt_count <-_raw_spin_unlock
            bash-1977  [000] .... 17284.993657: filp_close <-__close_fd
            bash-1977  [000] .... 17284.993657: dnotify_flush <-filp_close
            sshd-1974  [003] .... 17284.993658: sys_select <-system_call_fastpath
            ....”…””}”hjØ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÁhj¹  h²hubhÌ)”}”(hXX  A header is printed with the tracer name that is represented by
the trace. In this case the tracer is "function". Then it shows the
number of events in the buffer as well as the total number of entries
that were written. The difference is the number of entries that were
lost due to the buffer filling up (250280 - 140080 = 110200 events
lost).”h]”hX\  A header is printed with the tracer name that is represented by
the trace. In this case the tracer is â€œfunctionâ€. Then it shows the
number of events in the buffer as well as the total number of entries
that were written. The difference is the number of entries that were
lost due to the buffer filling up (250280 - 140080 = 110200 events
lost).”…””}”(hjæ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MØhj¹  h²hubhÌ)”}”(hX~  The header explains the content of the events. Task name "bash", the task
PID "1977", the CPU that it was running on "000", the latency format
(explained below), the timestamp in <secs>.<usecs> format, the
function name that was traced "sys_close" and the parent function that
called this function "system_call_fastpath". The timestamp is the time
at which the function was entered.”h]”hX’  The header explains the content of the events. Task name â€œbashâ€, the task
PID â€œ1977â€, the CPU that it was running on â€œ000â€, the latency format
(explained below), the timestamp in <secs>.<usecs> format, the
function name that was traced â€œsys_closeâ€ and the parent function that
called this function â€œsystem_call_fastpathâ€. The timestamp is the time
at which the function was entered.”…””}”(hjô  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mßhj¹  h²hubeh}”(h]”Œoutput-format”ah ]”h"]”Œoutput format:”ah$]”h&]”uh1hµhh·h²hh³hÊh´M½ubh¶)”}”(hhh]”(h»)”}”(hŒLatency trace format”h]”hŒLatency trace format”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj
  h²hh³hÊh´MçubhÌ)”}”(hŒ¼When the latency-format option is enabled or when one of the latency
tracers is set, the trace file gives somewhat more information to see
why a latency happened. Here is a typical trace::”h]”hŒ»When the latency-format option is enabled or when one of the latency
tracers is set, the trace file gives somewhat more information to see
why a latency happened. Here is a typical trace:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Méhj
  h²hubj´  )”}”(hX¦  # tracer: irqsoff
#
# irqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 259 us, #4/4, CPU#2 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: ps-6143 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: __lock_task_sighand
#  => ended at:   _raw_spin_unlock_irqrestore
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
      ps-6143    2d...    0us!: trace_hardirqs_off <-__lock_task_sighand
      ps-6143    2d..1  259us+: trace_hardirqs_on <-_raw_spin_unlock_irqrestore
      ps-6143    2d..1  263us+: time_hardirqs_on <-_raw_spin_unlock_irqrestore
      ps-6143    2d..1  306us : <stack trace>
 => trace_hardirqs_on_caller
 => trace_hardirqs_on
 => _raw_spin_unlock_irqrestore
 => do_task_stat
 => proc_tgid_stat
 => proc_single_show
 => seq_read
 => vfs_read
 => sys_read
 => system_call_fastpath”•‰      h]”hX¦  # tracer: irqsoff
#
# irqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 259 us, #4/4, CPU#2 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: ps-6143 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: __lock_task_sighand
#  => ended at:   _raw_spin_unlock_irqrestore
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
      ps-6143    2d...    0us!: trace_hardirqs_off <-__lock_task_sighand
      ps-6143    2d..1  259us+: trace_hardirqs_on <-_raw_spin_unlock_irqrestore
      ps-6143    2d..1  263us+: time_hardirqs_on <-_raw_spin_unlock_irqrestore
      ps-6143    2d..1  306us : <stack trace>
 => trace_hardirqs_on_caller
 => trace_hardirqs_on
 => _raw_spin_unlock_irqrestore
 => do_task_stat
 => proc_tgid_stat
 => proc_single_show
 => seq_read
 => vfs_read
 => sys_read
 => system_call_fastpath”…””}”hj)  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Míhj
  h²hubhÌ)”}”(hXÒ  This shows that the current tracer is "irqsoff" tracing the time
for which interrupts were disabled. It gives the trace version (which
never changes) and the version of the kernel upon which this was executed on
(3.8). Then it displays the max latency in microseconds (259 us). The number
of trace entries displayed and the total number (both are four: #4/4).
VP, KP, SP, and HP are always zero and are reserved for later use.
#P is the number of online CPUs (#P:4).”h]”hXÖ  This shows that the current tracer is â€œirqsoffâ€ tracing the time
for which interrupts were disabled. It gives the trace version (which
never changes) and the version of the kernel upon which this was executed on
(3.8). Then it displays the max latency in microseconds (259 us). The number
of trace entries displayed and the total number (both are four: #4/4).
VP, KP, SP, and HP are always zero and are reserved for later use.
#P is the number of online CPUs (#P:4).”…””}”(hj7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj
  h²hubhÌ)”}”(hŒSThe task is the process that was running when the latency
occurred. (ps pid: 6143).”h]”hŒSThe task is the process that was running when the latency
occurred. (ps pid: 6143).”…””}”(hjE  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj
  h²hubhÌ)”}”(hŒ|The start and stop (the functions in which the interrupts were
disabled and enabled respectively) that caused the latencies:”h]”hŒ|The start and stop (the functions in which the interrupts were
disabled and enabled respectively) that caused the latencies:”…””}”(hjS  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj
  h²hubjh  )”}”(hŒ}- __lock_task_sighand is where the interrupts were disabled.
- _raw_spin_unlock_irqrestore is where they were enabled again.
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ:__lock_task_sighand is where the interrupts were disabled.”h]”hÌ)”}”(hjj  h]”hŒ:__lock_task_sighand is where the interrupts were disabled.”…””}”(hjl  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjh  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hje  ubj”  )”}”(hŒ>_raw_spin_unlock_irqrestore is where they were enabled again.
”h]”hÌ)”}”(hŒ=_raw_spin_unlock_irqrestore is where they were enabled again.”h]”hŒ=_raw_spin_unlock_irqrestore is where they were enabled again.”…””}”(hjƒ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hje  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´Mhja  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj
  h²hubhÌ)”}”(hŒYThe next lines after the header are the trace itself. The header
explains which is which.”h]”hŒYThe next lines after the header are the trace itself. The header
explains which is which.”…””}”(hj£  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M"hj
  h²hubjh  )”}”(hX  cmd: The name of the process in the trace.

pid: The PID of that process.

CPU#: The CPU which the process was running on.

irqs-off: 'd' interrupts are disabled. '.' otherwise.

need-resched:
      - 'B' all, TIF_NEED_RESCHED, PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,
      - 'N' both TIF_NEED_RESCHED and PREEMPT_NEED_RESCHED is set,
      - 'n' only TIF_NEED_RESCHED is set,
      - 'p' only PREEMPT_NEED_RESCHED is set,
      - 'L' both PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,
      - 'b' both TIF_NEED_RESCHED and TIF_RESCHED_LAZY is set,
      - 'l' only TIF_RESCHED_LAZY is set
      - '.' otherwise.

hardirq/softirq:
      - 'Z' - NMI occurred inside a hardirq
      - 'z' - NMI is running
      - 'H' - hard irq occurred inside a softirq.
      - 'h' - hard irq is running
      - 's' - soft irq is running
      - '.' - normal context.

preempt-depth: The level of preempt_disabled
”h]”(hÌ)”}”(hŒ*cmd: The name of the process in the trace.”h]”hŒ*cmd: The name of the process in the trace.”…””}”(hjµ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M%hj±  ubhÌ)”}”(hŒpid: The PID of that process.”h]”hŒpid: The PID of that process.”…””}”(hjÃ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M'hj±  ubhÌ)”}”(hŒ/CPU#: The CPU which the process was running on.”h]”hŒ/CPU#: The CPU which the process was running on.”…””}”(hjÑ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M)hj±  ubhÌ)”}”(hŒ5irqs-off: 'd' interrupts are disabled. '.' otherwise.”h]”hŒ=irqs-off: â€˜dâ€™ interrupts are disabled. â€˜.â€™ otherwise.”…””}”(hjß  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M+hj±  ubjŽ  )”}”(hhh]”(j“  )”}”(hX  need-resched:
- 'B' all, TIF_NEED_RESCHED, PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,
- 'N' both TIF_NEED_RESCHED and PREEMPT_NEED_RESCHED is set,
- 'n' only TIF_NEED_RESCHED is set,
- 'p' only PREEMPT_NEED_RESCHED is set,
- 'L' both PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,
- 'b' both TIF_NEED_RESCHED and TIF_RESCHED_LAZY is set,
- 'l' only TIF_RESCHED_LAZY is set
- '.' otherwise.
”h]”(j™  )”}”(hŒneed-resched:”h]”hŒneed-resched:”…””}”(hjô  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M5hjð  ubj©  )”}”(hhh]”j  )”}”(hhh]”(j”  )”}”(hŒL'B' all, TIF_NEED_RESCHED, PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,”h]”hÌ)”}”(hj
  h]”hŒPâ€˜Bâ€™ all, TIF_NEED_RESCHED, PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M.hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ:'N' both TIF_NEED_RESCHED and PREEMPT_NEED_RESCHED is set,”h]”hÌ)”}”(hj!  h]”hŒ>â€˜Nâ€™ both TIF_NEED_RESCHED and PREEMPT_NEED_RESCHED is set,”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M/hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ!'n' only TIF_NEED_RESCHED is set,”h]”hÌ)”}”(hj8  h]”hŒ%â€˜nâ€™ only TIF_NEED_RESCHED is set,”…””}”(hj:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M0hj6  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ%'p' only PREEMPT_NEED_RESCHED is set,”h]”hÌ)”}”(hjO  h]”hŒ)â€˜pâ€™ only PREEMPT_NEED_RESCHED is set,”…””}”(hjQ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M1hjM  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ:'L' both PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,”h]”hÌ)”}”(hjf  h]”hŒ>â€˜Lâ€™ both PREEMPT_NEED_RESCHED and TIF_RESCHED_LAZY is set,”…””}”(hjh  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M2hjd  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ6'b' both TIF_NEED_RESCHED and TIF_RESCHED_LAZY is set,”h]”hÌ)”}”(hj}  h]”hŒ:â€˜bâ€™ both TIF_NEED_RESCHED and TIF_RESCHED_LAZY is set,”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M3hj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ 'l' only TIF_RESCHED_LAZY is set”h]”hÌ)”}”(hj”  h]”hŒ$â€˜lâ€™ only TIF_RESCHED_LAZY is set”…””}”(hj–  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M4hj’  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ'.' otherwise.
”h]”hÌ)”}”(hŒ'.' otherwise.”h]”hŒâ€˜.â€™ otherwise.”…””}”(hj­  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M5hj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´M.hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjð  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M5hjí  ubj“  )”}”(hŒÊhardirq/softirq:
- 'Z' - NMI occurred inside a hardirq
- 'z' - NMI is running
- 'H' - hard irq occurred inside a softirq.
- 'h' - hard irq is running
- 's' - soft irq is running
- '.' - normal context.
”h]”(j™  )”}”(hŒhardirq/softirq:”h]”hŒhardirq/softirq:”…””}”(hj×  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M=hjÓ  ubj©  )”}”(hhh]”j  )”}”(hhh]”(j”  )”}”(hŒ#'Z' - NMI occurred inside a hardirq”h]”hÌ)”}”(hjí  h]”hŒ'â€˜Zâ€™ - NMI occurred inside a hardirq”…””}”(hjï  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M8hjë  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjè  ubj”  )”}”(hŒ'z' - NMI is running”h]”hÌ)”}”(hj  h]”hŒâ€˜zâ€™ - NMI is running”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M9hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjè  ubj”  )”}”(hŒ)'H' - hard irq occurred inside a softirq.”h]”hÌ)”}”(hj  h]”hŒ-â€˜Hâ€™ - hard irq occurred inside a softirq.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M:hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjè  ubj”  )”}”(hŒ'h' - hard irq is running”h]”hÌ)”}”(hj2  h]”hŒâ€˜hâ€™ - hard irq is running”…””}”(hj4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M;hj0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjè  ubj”  )”}”(hŒ's' - soft irq is running”h]”hÌ)”}”(hjI  h]”hŒâ€˜sâ€™ - soft irq is running”…””}”(hjK  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M<hjG  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjè  ubj”  )”}”(hŒ'.' - normal context.
”h]”hÌ)”}”(hŒ'.' - normal context.”h]”hŒâ€˜.â€™ - normal context.”…””}”(hjb  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M=hj^  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjè  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´M8hjå  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÓ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M=hjí  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj±  ubhÌ)”}”(hŒ,preempt-depth: The level of preempt_disabled”h]”hŒ,preempt-depth: The level of preempt_disabled”…””}”(hjŽ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M?hj±  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M%hj
  h²hubhÌ)”}”(hŒ5The above is mostly meaningful for kernel developers.”h]”hŒ5The above is mostly meaningful for kernel developers.”…””}”(hj¢  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MAhj
  h²hubjh  )”}”(hX´  time:
      When the latency-format option is enabled, the trace file
      output includes a timestamp relative to the start of the
      trace. This differs from the output when latency-format
      is disabled, which includes an absolute timestamp.

delay:
      This is just to help catch your eye a bit better. And
      needs to be fixed to be only relative to the same CPU.
      The marks are determined by the difference between this
      current trace and the next trace.

        - '$' - greater than 1 second
        - '@' - greater than 100 millisecond
        - '*' - greater than 10 millisecond
        - '#' - greater than 1000 microsecond
        - '!' - greater than 100 microsecond
        - '+' - greater than 10 microsecond
        - ' ' - less than or equal to 10 microsecond.

The rest is the same as the 'trace' file.

Note, the latency tracers will usually end with a back trace
to easily find where the latency occurred.
”h]”(jŽ  )”}”(hhh]”(j“  )”}”(hŒätime:
When the latency-format option is enabled, the trace file
output includes a timestamp relative to the start of the
trace. This differs from the output when latency-format
is disabled, which includes an absolute timestamp.
”h]”(j™  )”}”(hŒtime:”h]”hŒtime:”…””}”(hj»  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MGhj·  ubj©  )”}”(hhh]”hÌ)”}”(hŒÝWhen the latency-format option is enabled, the trace file
output includes a timestamp relative to the start of the
trace. This differs from the output when latency-format
is disabled, which includes an absolute timestamp.”h]”hŒÝWhen the latency-format option is enabled, the trace file
output includes a timestamp relative to the start of the
trace. This differs from the output when latency-format
is disabled, which includes an absolute timestamp.”…””}”(hjÌ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MDhjÉ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj·  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MGhj´  ubj“  )”}”(hXá  delay:
This is just to help catch your eye a bit better. And
needs to be fixed to be only relative to the same CPU.
The marks are determined by the difference between this
current trace and the next trace.

  - '$' - greater than 1 second
  - '@' - greater than 100 millisecond
  - '*' - greater than 10 millisecond
  - '#' - greater than 1000 microsecond
  - '!' - greater than 100 microsecond
  - '+' - greater than 10 microsecond
  - ' ' - less than or equal to 10 microsecond.
”h]”(j™  )”}”(hŒdelay:”h]”hŒdelay:”…””}”(hjê  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MUhjæ  ubj©  )”}”(hhh]”(hÌ)”}”(hŒÆThis is just to help catch your eye a bit better. And
needs to be fixed to be only relative to the same CPU.
The marks are determined by the difference between this
current trace and the next trace.”h]”hŒÆThis is just to help catch your eye a bit better. And
needs to be fixed to be only relative to the same CPU.
The marks are determined by the difference between this
current trace and the next trace.”…””}”(hjû  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MJhjø  ubjh  )”}”(hX  - '$' - greater than 1 second
- '@' - greater than 100 millisecond
- '*' - greater than 10 millisecond
- '#' - greater than 1000 microsecond
- '!' - greater than 100 microsecond
- '+' - greater than 10 microsecond
- ' ' - less than or equal to 10 microsecond.
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ'$' - greater than 1 second”h]”hÌ)”}”(hj  h]”hŒâ€˜$â€™ - greater than 1 second”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MOhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ"'@' - greater than 100 millisecond”h]”hÌ)”}”(hj)  h]”hŒ&â€˜@â€™ - greater than 100 millisecond”…””}”(hj+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MPhj'  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ!'*' - greater than 10 millisecond”h]”hÌ)”}”(hj@  h]”hŒ%â€˜*â€™ - greater than 10 millisecond”…””}”(hjB  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MQhj>  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ#'#' - greater than 1000 microsecond”h]”hÌ)”}”(hjW  h]”hŒ'â€˜#â€™ - greater than 1000 microsecond”…””}”(hjY  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MRhjU  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ"'!' - greater than 100 microsecond”h]”hÌ)”}”(hjn  h]”hŒ&â€˜!â€™ - greater than 100 microsecond”…””}”(hjp  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MShjl  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ!'+' - greater than 10 microsecond”h]”hÌ)”}”(hj…  h]”hŒ%â€˜+â€™ - greater than 10 microsecond”…””}”(hj‡  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MThjƒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubj”  )”}”(hŒ,' ' - less than or equal to 10 microsecond.
”h]”hÌ)”}”(hŒ+' ' - less than or equal to 10 microsecond.”h]”hŒ/â€˜ â€˜ - less than or equal to 10 microsecond.”…””}”(hjž  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MUhjš  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´MOhj	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MOhjø  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjæ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MUhj´  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj°  ubhÌ)”}”(hŒ)The rest is the same as the 'trace' file.”h]”hŒ-The rest is the same as the â€˜traceâ€™ file.”…””}”(hjÐ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MWhj°  ubhÌ)”}”(hŒgNote, the latency tracers will usually end with a back trace
to easily find where the latency occurred.”h]”hŒgNote, the latency tracers will usually end with a back trace
to easily find where the latency occurred.”…””}”(hjÞ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MYhj°  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MChj
  h²hubeh}”(h]”Œlatency-trace-format”ah ]”h"]”Œlatency trace format”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mçubh¶)”}”(hhh]”(h»)”}”(hŒtrace_options”h]”hŒtrace_options”…””}”(hjý  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjú  h²hh³hÊh´M]ubhÌ)”}”(hŒ¶The trace_options file (or the options directory) is used to control
what gets printed in the trace output, or manipulate the tracers.
To see what is available, simply cat the file::”h]”hŒµThe trace_options file (or the options directory) is used to control
what gets printed in the trace output, or manipulate the tracers.
To see what is available, simply cat the file:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M_hjú  h²hubj´  )”}”(hX  cat trace_options
      print-parent
      nosym-offset
      nosym-addr
      noverbose
      noraw
      nohex
      nobin
      noblock
      nofields
      trace_printk
      annotate
      nouserstacktrace
      nosym-userobj
      noprintk-msg-only
      context-info
      nolatency-format
      record-cmd
      norecord-tgid
      overwrite
      nodisable_on_free
      irq-info
      markers
      noevent-fork
      function-trace
      nofunction-fork
      nodisplay-graph
      nostacktrace
      nobranch”h]”hX  cat trace_options
      print-parent
      nosym-offset
      nosym-addr
      noverbose
      noraw
      nohex
      nobin
      noblock
      nofields
      trace_printk
      annotate
      nouserstacktrace
      nosym-userobj
      noprintk-msg-only
      context-info
      nolatency-format
      record-cmd
      norecord-tgid
      overwrite
      nodisable_on_free
      irq-info
      markers
      noevent-fork
      function-trace
      nofunction-fork
      nodisplay-graph
      nostacktrace
      nobranch”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mchjú  h²hubhÌ)”}”(hŒGTo disable one of the options, echo in the option prepended with
"no"::”h]”hŒJTo disable one of the options, echo in the option prepended with
â€œnoâ€:”…””}”(hj'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjú  h²hubj´  )”}”(hŒ#echo noprint-parent > trace_options”h]”hŒ#echo noprint-parent > trace_options”…””}”hj5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M„hjú  h²hubhÌ)”}”(hŒ)To enable an option, leave off the "no"::”h]”hŒ,To enable an option, leave off the â€œnoâ€:”…””}”(hjC  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M†hjú  h²hubj´  )”}”(hŒecho sym-offset > trace_options”h]”hŒecho sym-offset > trace_options”…””}”hjQ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mˆhjú  h²hubhÌ)”}”(hŒHere are the available options:”h]”hŒHere are the available options:”…””}”(hj_  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŠhjú  h²hubjh  )”}”(hXÓ$  print-parent
      On function traces, display the calling (parent)
      function as well as the function being traced.
      ::

        print-parent:
         bash-4000  [01]  1477.606694: simple_strtoul <-kstrtoul

        noprint-parent:
         bash-4000  [01]  1477.606694: simple_strtoul


sym-offset
      Display not only the function name, but also the
      offset in the function. For example, instead of
      seeing just "ktime_get", you will see
      "ktime_get+0xb/0x20".
      ::

        sym-offset:
         bash-4000  [01]  1477.606694: simple_strtoul+0x6/0xa0

sym-addr
      This will also display the function address as well
      as the function name.
      ::

        sym-addr:
         bash-4000  [01]  1477.606694: simple_strtoul <c0339346>

verbose
      This deals with the trace file when the
      latency-format option is enabled.
      ::

          bash  4000 1 0 00000000 00010a95 [58127d26] 1720.415ms \
          (+0.000ms): simple_strtoul (kstrtoul)

raw
      This will display raw numbers. This option is best for
      use with user applications that can translate the raw
      numbers better than having it done in the kernel.

hex
      Similar to raw, but the numbers will be in a hexadecimal format.

bin
      This will print out the formats in raw binary.

block
      When set, reading trace_pipe will not block when polled.

fields
      Print the fields as described by their types. This is a better
      option than using hex, bin or raw, as it gives a better parsing
      of the content of the event.

trace_printk
      Can disable trace_printk() from writing into the buffer.

trace_printk_dest
      Set to have trace_printk() and similar internal tracing functions
      write into this instance. Note, only one trace instance can have
      this set. By setting this flag, it clears the trace_printk_dest flag
      of the instance that had it set previously. By default, the top
      level trace has this set, and will get it set again if another
      instance has it set then clears it.

      This flag cannot be cleared by the top level instance, as it is the
      default instance. The only way the top level instance has this flag
      cleared, is by it being set in another instance.

copy_trace_marker
      If there are applications that hard code writing into the top level
      trace_marker file (/sys/kernel/tracing/trace_marker or trace_marker_raw),
      and the tooling would like it to go into an instance, this option can
      be used. Create an instance and set this option, and then all writes
      into the top level trace_marker file will also be redirected into this
      instance.

      Note, by default this option is set for the top level instance. If it
      is disabled, then writes to the trace_marker or trace_marker_raw files
      will not be written into the top level file. If no instance has this
      option set, then a write will error with the errno of ENODEV.

annotate
      It is sometimes confusing when the CPU buffers are full
      and one CPU buffer had a lot of events recently, thus
      a shorter time frame, were another CPU may have only had
      a few events, which lets it have older events. When
      the trace is reported, it shows the oldest events first,
      and it may look like only one CPU ran (the one with the
      oldest events). When the annotate option is set, it will
      display when a new CPU buffer started::

                        <idle>-0     [001] dNs4 21169.031481: wake_up_idle_cpu <-add_timer_on
                        <idle>-0     [001] dNs4 21169.031482: _raw_spin_unlock_irqrestore <-add_timer_on
                        <idle>-0     [001] .Ns4 21169.031484: sub_preempt_count <-_raw_spin_unlock_irqrestore
              ##### CPU 2 buffer started ####
                        <idle>-0     [002] .N.1 21169.031484: rcu_idle_exit <-cpu_idle
                        <idle>-0     [001] .Ns3 21169.031484: _raw_spin_unlock <-clocksource_watchdog
                        <idle>-0     [001] .Ns3 21169.031485: sub_preempt_count <-_raw_spin_unlock

userstacktrace
      This option changes the trace. It records a
      stacktrace of the current user space thread after
      each trace event.

sym-userobj
      when user stacktrace are enabled, look up which
      object the address belongs to, and print a
      relative address. This is especially useful when
      ASLR is on, otherwise you don't get a chance to
      resolve the address to object/file/line after
      the app is no longer running

      The lookup is performed when you read
      trace,trace_pipe. Example::

                a.out-1623  [000] 40874.465068: /root/a.out[+0x480] <-/root/a.out[+0
                x494] <- /root/a.out[+0x4a8] <- /lib/libc-2.7.so[+0x1e1a6]


printk-msg-only
      When set, trace_printk()s will only show the format
      and not their parameters (if trace_bprintk() or
      trace_bputs() was used to save the trace_printk()).

context-info
      Show only the event data. Hides the comm, PID,
      timestamp, CPU, and other useful data.

latency-format
      This option changes the trace output. When it is enabled,
      the trace displays additional information about the
      latency, as described in "Latency trace format".

pause-on-trace
      When set, opening the trace file for read, will pause
      writing to the ring buffer (as if tracing_on was set to zero).
      This simulates the original behavior of the trace file.
      When the file is closed, tracing will be enabled again.

hash-ptr
      When set, "%p" in the event printk format displays the
      hashed pointer value instead of real address.
      This will be useful if you want to find out which hashed
      value is corresponding to the real value in trace log.

bitmask-list
      When enabled, bitmasks are displayed as a human-readable list of
      ranges (e.g., 0,2-5,7) using the printk "%*pbl" format specifier.
      When disabled (the default), bitmasks are displayed in the
      traditional hexadecimal bitmap representation. The list format is
      particularly useful for tracing CPU masks and other large bitmasks
      where individual bit positions are more meaningful than their
      hexadecimal encoding.

record-cmd
      When any event or tracer is enabled, a hook is enabled
      in the sched_switch trace point to fill comm cache
      with mapped pids and comms. But this may cause some
      overhead, and if you only care about pids, and not the
      name of the task, disabling this option can lower the
      impact of tracing. See "saved_cmdlines".

record-tgid
      When any event or tracer is enabled, a hook is enabled
      in the sched_switch trace point to fill the cache of
      mapped Thread Group IDs (TGID) mapping to pids. See
      "saved_tgids".

overwrite
      This controls what happens when the trace buffer is
      full. If "1" (default), the oldest events are
      discarded and overwritten. If "0", then the newest
      events are discarded.
      (see per_cpu/cpu0/stats for overrun and dropped)

disable_on_free
      When the free_buffer is closed, tracing will
      stop (tracing_on set to 0).

irq-info
      Shows the interrupt, preempt count, need resched data.
      When disabled, the trace looks like::

              # tracer: function
              #
              # entries-in-buffer/entries-written: 144405/9452052   #P:4
              #
              #           TASK-PID   CPU#      TIMESTAMP  FUNCTION
              #              | |       |          |         |
                        <idle>-0     [002]  23636.756054: ttwu_do_activate.constprop.89 <-try_to_wake_up
                        <idle>-0     [002]  23636.756054: activate_task <-ttwu_do_activate.constprop.89
                        <idle>-0     [002]  23636.756055: enqueue_task <-activate_task


markers
      When set, the trace_marker is writable (only by root).
      When disabled, the trace_marker will error with EINVAL
      on write.

event-fork
      When set, tasks with PIDs listed in set_event_pid will have
      the PIDs of their children added to set_event_pid when those
      tasks fork. Also, when tasks with PIDs in set_event_pid exit,
      their PIDs will be removed from the file.

      This affects PIDs listed in set_event_notrace_pid as well.

function-trace
      The latency tracers will enable function tracing
      if this option is enabled (default it is). When
      it is disabled, the latency tracers do not trace
      functions. This keeps the overhead of the tracer down
      when performing latency tests.

function-fork
      When set, tasks with PIDs listed in set_ftrace_pid will
      have the PIDs of their children added to set_ftrace_pid
      when those tasks fork. Also, when tasks with PIDs in
      set_ftrace_pid exit, their PIDs will be removed from the
      file.

      This affects PIDs in set_ftrace_notrace_pid as well.

display-graph
      When set, the latency tracers (irqsoff, wakeup, etc) will
      use function graph tracing instead of function tracing.

stacktrace
      When set, a stack trace is recorded after any trace event
      is recorded.

branch
      Enable branch tracing with the tracer. This enables branch
      tracer along with the currently set tracer. Enabling this
      with the "nop" tracer is the same as just enabling the
      "branch" tracer.
”h]”jŽ  )”}”(hhh]”(j“  )”}”(hX   print-parent
On function traces, display the calling (parent)
function as well as the function being traced.
::

  print-parent:
   bash-4000  [01]  1477.606694: simple_strtoul <-kstrtoul

  noprint-parent:
   bash-4000  [01]  1477.606694: simple_strtoul

”h]”(j™  )”}”(hŒprint-parent”h]”hŒprint-parent”…””}”(hjx  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M–hjt  ubj©  )”}”(hhh]”(hÌ)”}”(hŒbOn function traces, display the calling (parent)
function as well as the function being traced.
::”h]”hŒ_On function traces, display the calling (parent)
function as well as the function being traced.”…””}”(hj‰  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj†  ubj´  )”}”(hŒ…print-parent:
 bash-4000  [01]  1477.606694: simple_strtoul <-kstrtoul

noprint-parent:
 bash-4000  [01]  1477.606694: simple_strtoul”h]”hŒ…print-parent:
 bash-4000  [01]  1477.606694: simple_strtoul <-kstrtoul

noprint-parent:
 bash-4000  [01]  1477.606694: simple_strtoul”…””}”hj—  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M‘hj†  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjt  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M–hjq  ubj“  )”}”(hŒósym-offset
Display not only the function name, but also the
offset in the function. For example, instead of
seeing just "ktime_get", you will see
"ktime_get+0xb/0x20".
::

  sym-offset:
   bash-4000  [01]  1477.606694: simple_strtoul+0x6/0xa0
”h]”(j™  )”}”(hŒ
sym-offset”h]”hŒ
sym-offset”…””}”(hjµ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M hj±  ubj©  )”}”(hhh]”(hÌ)”}”(hŒŸDisplay not only the function name, but also the
offset in the function. For example, instead of
seeing just "ktime_get", you will see
"ktime_get+0xb/0x20".
::”h]”hŒ¤Display not only the function name, but also the
offset in the function. For example, instead of
seeing just â€œktime_getâ€, you will see
â€œktime_get+0xb/0x20â€.”…””}”(hjÆ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M™hjÃ  ubj´  )”}”(hŒBsym-offset:
 bash-4000  [01]  1477.606694: simple_strtoul+0x6/0xa0”h]”hŒBsym-offset:
 bash-4000  [01]  1477.606694: simple_strtoul+0x6/0xa0”…””}”hjÔ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MŸhjÃ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj±  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M hjq  ubj“  )”}”(hŒžsym-addr
This will also display the function address as well
as the function name.
::

  sym-addr:
   bash-4000  [01]  1477.606694: simple_strtoul <c0339346>
”h]”(j™  )”}”(hŒsym-addr”h]”hŒsym-addr”…””}”(hjò  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M¨hjî  ubj©  )”}”(hhh]”(hÌ)”}”(hŒLThis will also display the function address as well
as the function name.
::”h]”hŒIThis will also display the function address as well
as the function name.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M£hj   ubj´  )”}”(hŒBsym-addr:
 bash-4000  [01]  1477.606694: simple_strtoul <c0339346>”h]”hŒBsym-addr:
 bash-4000  [01]  1477.606694: simple_strtoul <c0339346>”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M§hj   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjî  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M¨hjq  ubj“  )”}”(hŒ½verbose
This deals with the trace file when the
latency-format option is enabled.
::

    bash  4000 1 0 00000000 00010a95 [58127d26] 1720.415ms \
    (+0.000ms): simple_strtoul (kstrtoul)
”h]”(j™  )”}”(hŒverbose”h]”hŒverbose”…””}”(hj/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M°hj+  ubj©  )”}”(hhh]”(hÌ)”}”(hŒLThis deals with the trace file when the
latency-format option is enabled.
::”h]”hŒIThis deals with the trace file when the
latency-format option is enabled.”…””}”(hj@  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M«hj=  ubj´  )”}”(hŒ^bash  4000 1 0 00000000 00010a95 [58127d26] 1720.415ms \
(+0.000ms): simple_strtoul (kstrtoul)”h]”hŒ^bash  4000 1 0 00000000 00010a95 [58127d26] 1720.415ms \
(+0.000ms): simple_strtoul (kstrtoul)”…””}”hjN  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¯hj=  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj+  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M°hjq  ubj“  )”}”(hŒ£raw
This will display raw numbers. This option is best for
use with user applications that can translate the raw
numbers better than having it done in the kernel.
”h]”(j™  )”}”(hŒraw”h]”hŒraw”…””}”(hjl  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mµhjh  ubj©  )”}”(hhh]”hÌ)”}”(hŒžThis will display raw numbers. This option is best for
use with user applications that can translate the raw
numbers better than having it done in the kernel.”h]”hŒžThis will display raw numbers. This option is best for
use with user applications that can translate the raw
numbers better than having it done in the kernel.”…””}”(hj}  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M³hjz  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjh  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mµhjq  ubj“  )”}”(hŒEhex
Similar to raw, but the numbers will be in a hexadecimal format.
”h]”(j™  )”}”(hŒhex”h]”hŒhex”…””}”(hj›  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M¸hj—  ubj©  )”}”(hhh]”hÌ)”}”(hŒ@Similar to raw, but the numbers will be in a hexadecimal format.”h]”hŒ@Similar to raw, but the numbers will be in a hexadecimal format.”…””}”(hj¬  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¸hj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj—  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M¸hjq  ubj“  )”}”(hŒ3bin
This will print out the formats in raw binary.
”h]”(j™  )”}”(hŒbin”h]”hŒbin”…””}”(hjÊ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M»hjÆ  ubj©  )”}”(hhh]”hÌ)”}”(hŒ.This will print out the formats in raw binary.”h]”hŒ.This will print out the formats in raw binary.”…””}”(hjÛ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M»hjØ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÆ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M»hjq  ubj“  )”}”(hŒ?block
When set, reading trace_pipe will not block when polled.
”h]”(j™  )”}”(hŒblock”h]”hŒblock”…””}”(hjù  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M¾hjõ  ubj©  )”}”(hhh]”hÌ)”}”(hŒ8When set, reading trace_pipe will not block when polled.”h]”hŒ8When set, reading trace_pipe will not block when polled.”…””}”(hj
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¾hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjõ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M¾hjq  ubj“  )”}”(hŒ£fields
Print the fields as described by their types. This is a better
option than using hex, bin or raw, as it gives a better parsing
of the content of the event.
”h]”(j™  )”}”(hŒfields”h]”hŒfields”…””}”(hj(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÃhj$  ubj©  )”}”(hhh]”hÌ)”}”(hŒ›Print the fields as described by their types. This is a better
option than using hex, bin or raw, as it gives a better parsing
of the content of the event.”h]”hŒ›Print the fields as described by their types. This is a better
option than using hex, bin or raw, as it gives a better parsing
of the content of the event.”…””}”(hj9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÁhj6  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj$  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÃhjq  ubj“  )”}”(hŒFtrace_printk
Can disable trace_printk() from writing into the buffer.
”h]”(j™  )”}”(hŒtrace_printk”h]”hŒtrace_printk”…””}”(hjW  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÆhjS  ubj©  )”}”(hhh]”hÌ)”}”(hŒ8Can disable trace_printk() from writing into the buffer.”h]”hŒ8Can disable trace_printk() from writing into the buffer.”…””}”(hjh  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÆhje  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjS  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÆhjq  ubj“  )”}”(hX7  trace_printk_dest
Set to have trace_printk() and similar internal tracing functions
write into this instance. Note, only one trace instance can have
this set. By setting this flag, it clears the trace_printk_dest flag
of the instance that had it set previously. By default, the top
level trace has this set, and will get it set again if another
instance has it set then clears it.

This flag cannot be cleared by the top level instance, as it is the
default instance. The only way the top level instance has this flag
cleared, is by it being set in another instance.
”h]”(j™  )”}”(hŒtrace_printk_dest”h]”hŒtrace_printk_dest”…””}”(hj†  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÒhj‚  ubj©  )”}”(hhh]”(hÌ)”}”(hXj  Set to have trace_printk() and similar internal tracing functions
write into this instance. Note, only one trace instance can have
this set. By setting this flag, it clears the trace_printk_dest flag
of the instance that had it set previously. By default, the top
level trace has this set, and will get it set again if another
instance has it set then clears it.”h]”hXj  Set to have trace_printk() and similar internal tracing functions
write into this instance. Note, only one trace instance can have
this set. By setting this flag, it clears the trace_printk_dest flag
of the instance that had it set previously. By default, the top
level trace has this set, and will get it set again if another
instance has it set then clears it.”…””}”(hj—  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÉhj”  ubhÌ)”}”(hŒ¸This flag cannot be cleared by the top level instance, as it is the
default instance. The only way the top level instance has this flag
cleared, is by it being set in another instance.”h]”hŒ¸This flag cannot be cleared by the top level instance, as it is the
default instance. The only way the top level instance has this flag
cleared, is by it being set in another instance.”…””}”(hj¥  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÐhj”  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj‚  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÒhjq  ubj“  )”}”(hX  copy_trace_marker
If there are applications that hard code writing into the top level
trace_marker file (/sys/kernel/tracing/trace_marker or trace_marker_raw),
and the tooling would like it to go into an instance, this option can
be used. Create an instance and set this option, and then all writes
into the top level trace_marker file will also be redirected into this
instance.

Note, by default this option is set for the top level instance. If it
is disabled, then writes to the trace_marker or trace_marker_raw files
will not be written into the top level file. If no instance has this
option set, then a write will error with the errno of ENODEV.
”h]”(j™  )”}”(hŒcopy_trace_marker”h]”hŒcopy_trace_marker”…””}”(hjÃ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mßhj¿  ubj©  )”}”(hhh]”(hÌ)”}”(hXi  If there are applications that hard code writing into the top level
trace_marker file (/sys/kernel/tracing/trace_marker or trace_marker_raw),
and the tooling would like it to go into an instance, this option can
be used. Create an instance and set this option, and then all writes
into the top level trace_marker file will also be redirected into this
instance.”h]”hXi  If there are applications that hard code writing into the top level
trace_marker file (/sys/kernel/tracing/trace_marker or trace_marker_raw),
and the tooling would like it to go into an instance, this option can
be used. Create an instance and set this option, and then all writes
into the top level trace_marker file will also be redirected into this
instance.”…””}”(hjÔ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÕhjÑ  ubhÌ)”}”(hX  Note, by default this option is set for the top level instance. If it
is disabled, then writes to the trace_marker or trace_marker_raw files
will not be written into the top level file. If no instance has this
option set, then a write will error with the errno of ENODEV.”h]”hX  Note, by default this option is set for the top level instance. If it
is disabled, then writes to the trace_marker or trace_marker_raw files
will not be written into the top level file. If no instance has this
option set, then a write will error with the errno of ENODEV.”…””}”(hjâ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÜhjÑ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj¿  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mßhjq  ubj“  )”}”(hX  annotate
It is sometimes confusing when the CPU buffers are full
and one CPU buffer had a lot of events recently, thus
a shorter time frame, were another CPU may have only had
a few events, which lets it have older events. When
the trace is reported, it shows the oldest events first,
and it may look like only one CPU ran (the one with the
oldest events). When the annotate option is set, it will
display when a new CPU buffer started::

                  <idle>-0     [001] dNs4 21169.031481: wake_up_idle_cpu <-add_timer_on
                  <idle>-0     [001] dNs4 21169.031482: _raw_spin_unlock_irqrestore <-add_timer_on
                  <idle>-0     [001] .Ns4 21169.031484: sub_preempt_count <-_raw_spin_unlock_irqrestore
        ##### CPU 2 buffer started ####
                  <idle>-0     [002] .N.1 21169.031484: rcu_idle_exit <-cpu_idle
                  <idle>-0     [001] .Ns3 21169.031484: _raw_spin_unlock <-clocksource_watchdog
                  <idle>-0     [001] .Ns3 21169.031485: sub_preempt_count <-_raw_spin_unlock
”h]”(j™  )”}”(hŒannotate”h]”hŒannotate”…””}”(hj   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mñhjü  ubj©  )”}”(hhh]”(hÌ)”}”(hX¬  It is sometimes confusing when the CPU buffers are full
and one CPU buffer had a lot of events recently, thus
a shorter time frame, were another CPU may have only had
a few events, which lets it have older events. When
the trace is reported, it shows the oldest events first,
and it may look like only one CPU ran (the one with the
oldest events). When the annotate option is set, it will
display when a new CPU buffer started::”h]”hX«  It is sometimes confusing when the CPU buffers are full
and one CPU buffer had a lot of events recently, thus
a shorter time frame, were another CPU may have only had
a few events, which lets it have older events. When
the trace is reported, it shows the oldest events first,
and it may look like only one CPU ran (the one with the
oldest events). When the annotate option is set, it will
display when a new CPU buffer started:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mâhj  ubj´  )”}”(hX             <idle>-0     [001] dNs4 21169.031481: wake_up_idle_cpu <-add_timer_on
          <idle>-0     [001] dNs4 21169.031482: _raw_spin_unlock_irqrestore <-add_timer_on
          <idle>-0     [001] .Ns4 21169.031484: sub_preempt_count <-_raw_spin_unlock_irqrestore
##### CPU 2 buffer started ####
          <idle>-0     [002] .N.1 21169.031484: rcu_idle_exit <-cpu_idle
          <idle>-0     [001] .Ns3 21169.031484: _raw_spin_unlock <-clocksource_watchdog
          <idle>-0     [001] .Ns3 21169.031485: sub_preempt_count <-_raw_spin_unlock”h]”hX             <idle>-0     [001] dNs4 21169.031481: wake_up_idle_cpu <-add_timer_on
          <idle>-0     [001] dNs4 21169.031482: _raw_spin_unlock_irqrestore <-add_timer_on
          <idle>-0     [001] .Ns4 21169.031484: sub_preempt_count <-_raw_spin_unlock_irqrestore
##### CPU 2 buffer started ####
          <idle>-0     [002] .N.1 21169.031484: rcu_idle_exit <-cpu_idle
          <idle>-0     [001] .Ns3 21169.031484: _raw_spin_unlock <-clocksource_watchdog
          <idle>-0     [001] .Ns3 21169.031485: sub_preempt_count <-_raw_spin_unlock”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mëhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjü  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mñhjq  ubj“  )”}”(hŒuserstacktrace
This option changes the trace. It records a
stacktrace of the current user space thread after
each trace event.
”h]”(j™  )”}”(hŒuserstacktrace”h]”hŒuserstacktrace”…””}”(hj=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Möhj9  ubj©  )”}”(hhh]”hÌ)”}”(hŒoThis option changes the trace. It records a
stacktrace of the current user space thread after
each trace event.”h]”hŒoThis option changes the trace. It records a
stacktrace of the current user space thread after
each trace event.”…””}”(hjN  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MôhjK  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj9  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Möhjq  ubj“  )”}”(hXì  sym-userobj
when user stacktrace are enabled, look up which
object the address belongs to, and print a
relative address. This is especially useful when
ASLR is on, otherwise you don't get a chance to
resolve the address to object/file/line after
the app is no longer running

The lookup is performed when you read
trace,trace_pipe. Example::

          a.out-1623  [000] 40874.465068: /root/a.out[+0x480] <-/root/a.out[+0
          x494] <- /root/a.out[+0x4a8] <- /lib/libc-2.7.so[+0x1e1a6]

”h]”(j™  )”}”(hŒsym-userobj”h]”hŒsym-userobj”…””}”(hjl  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhjh  ubj©  )”}”(hhh]”(hÌ)”}”(hX  when user stacktrace are enabled, look up which
object the address belongs to, and print a
relative address. This is especially useful when
ASLR is on, otherwise you don't get a chance to
resolve the address to object/file/line after
the app is no longer running”h]”hX  when user stacktrace are enabled, look up which
object the address belongs to, and print a
relative address. This is especially useful when
ASLR is on, otherwise you donâ€™t get a chance to
resolve the address to object/file/line after
the app is no longer running”…””}”(hj}  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mùhjz  ubhÌ)”}”(hŒAThe lookup is performed when you read
trace,trace_pipe. Example::”h]”hŒ@The lookup is performed when you read
trace,trace_pipe. Example:”…””}”(hj‹  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hjz  ubj´  )”}”(hŒa.out-1623  [000] 40874.465068: /root/a.out[+0x480] <-/root/a.out[+0
x494] <- /root/a.out[+0x4a8] <- /lib/libc-2.7.so[+0x1e1a6]”h]”hŒa.out-1623  [000] 40874.465068: /root/a.out[+0x480] <-/root/a.out[+0
x494] <- /root/a.out[+0x4a8] <- /lib/libc-2.7.so[+0x1e1a6]”…””}”hj™  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhjz  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjh  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mhjq  ubj“  )”}”(hŒ¨printk-msg-only
When set, trace_printk()s will only show the format
and not their parameters (if trace_bprintk() or
trace_bputs() was used to save the trace_printk()).
”h]”(j™  )”}”(hŒprintk-msg-only”h]”hŒprintk-msg-only”…””}”(hj·  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M
hj³  ubj©  )”}”(hhh]”hÌ)”}”(hŒ—When set, trace_printk()s will only show the format
and not their parameters (if trace_bprintk() or
trace_bputs() was used to save the trace_printk()).”h]”hŒ—When set, trace_printk()s will only show the format
and not their parameters (if trace_bprintk() or
trace_bputs() was used to save the trace_printk()).”…””}”(hjÈ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjÅ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj³  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M
hjq  ubj“  )”}”(hŒccontext-info
Show only the event data. Hides the comm, PID,
timestamp, CPU, and other useful data.
”h]”(j™  )”}”(hŒcontext-info”h]”hŒcontext-info”…””}”(hjæ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhjâ  ubj©  )”}”(hhh]”hÌ)”}”(hŒUShow only the event data. Hides the comm, PID,
timestamp, CPU, and other useful data.”h]”hŒUShow only the event data. Hides the comm, PID,
timestamp, CPU, and other useful data.”…””}”(hj÷  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjô  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjâ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mhjq  ubj“  )”}”(hŒ®latency-format
This option changes the trace output. When it is enabled,
the trace displays additional information about the
latency, as described in "Latency trace format".
”h]”(j™  )”}”(hŒlatency-format”h]”hŒlatency-format”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhj  ubj©  )”}”(hhh]”hÌ)”}”(hŒžThis option changes the trace output. When it is enabled,
the trace displays additional information about the
latency, as described in "Latency trace format".”h]”hŒ¢This option changes the trace output. When it is enabled,
the trace displays additional information about the
latency, as described in â€œLatency trace formatâ€.”…””}”(hj&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mhjq  ubj“  )”}”(hŒôpause-on-trace
When set, opening the trace file for read, will pause
writing to the ring buffer (as if tracing_on was set to zero).
This simulates the original behavior of the trace file.
When the file is closed, tracing will be enabled again.
”h]”(j™  )”}”(hŒpause-on-trace”h]”hŒpause-on-trace”…””}”(hjD  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhj@  ubj©  )”}”(hhh]”hÌ)”}”(hŒäWhen set, opening the trace file for read, will pause
writing to the ring buffer (as if tracing_on was set to zero).
This simulates the original behavior of the trace file.
When the file is closed, tracing will be enabled again.”h]”hŒäWhen set, opening the trace file for read, will pause
writing to the ring buffer (as if tracing_on was set to zero).
This simulates the original behavior of the trace file.
When the file is closed, tracing will be enabled again.”…””}”(hjU  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjR  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj@  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mhjq  ubj“  )”}”(hŒÞhash-ptr
When set, "%p" in the event printk format displays the
hashed pointer value instead of real address.
This will be useful if you want to find out which hashed
value is corresponding to the real value in trace log.
”h]”(j™  )”}”(hŒhash-ptr”h]”hŒhash-ptr”…””}”(hjs  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhjo  ubj©  )”}”(hhh]”hÌ)”}”(hŒÔWhen set, "%p" in the event printk format displays the
hashed pointer value instead of real address.
This will be useful if you want to find out which hashed
value is corresponding to the real value in trace log.”h]”hŒØWhen set, â€œ%pâ€ in the event printk format displays the
hashed pointer value instead of real address.
This will be useful if you want to find out which hashed
value is corresponding to the real value in trace log.”…””}”(hj„  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjo  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mhjq  ubj“  )”}”(hX¤  bitmask-list
When enabled, bitmasks are displayed as a human-readable list of
ranges (e.g., 0,2-5,7) using the printk "%*pbl" format specifier.
When disabled (the default), bitmasks are displayed in the
traditional hexadecimal bitmap representation. The list format is
particularly useful for tracing CPU masks and other large bitmasks
where individual bit positions are more meaningful than their
hexadecimal encoding.
”h]”(j™  )”}”(hŒbitmask-list”h]”hŒbitmask-list”…””}”(hj¢  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M(hjž  ubj©  )”}”(hhh]”hÌ)”}”(hX–  When enabled, bitmasks are displayed as a human-readable list of
ranges (e.g., 0,2-5,7) using the printk "%*pbl" format specifier.
When disabled (the default), bitmasks are displayed in the
traditional hexadecimal bitmap representation. The list format is
particularly useful for tracing CPU masks and other large bitmasks
where individual bit positions are more meaningful than their
hexadecimal encoding.”h]”hXš  When enabled, bitmasks are displayed as a human-readable list of
ranges (e.g., 0,2-5,7) using the printk â€œ%*pblâ€ format specifier.
When disabled (the default), bitmasks are displayed in the
traditional hexadecimal bitmap representation. The list format is
particularly useful for tracing CPU masks and other large bitmasks
where individual bit positions are more meaningful than their
hexadecimal encoding.”…””}”(hj³  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M"hj°  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjž  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M(hjq  ubj“  )”}”(hX?  record-cmd
When any event or tracer is enabled, a hook is enabled
in the sched_switch trace point to fill comm cache
with mapped pids and comms. But this may cause some
overhead, and if you only care about pids, and not the
name of the task, disabling this option can lower the
impact of tracing. See "saved_cmdlines".
”h]”(j™  )”}”(hŒ
record-cmd”h]”hŒ
record-cmd”…””}”(hjÑ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M0hjÍ  ubj©  )”}”(hhh]”hÌ)”}”(hX3  When any event or tracer is enabled, a hook is enabled
in the sched_switch trace point to fill comm cache
with mapped pids and comms. But this may cause some
overhead, and if you only care about pids, and not the
name of the task, disabling this option can lower the
impact of tracing. See "saved_cmdlines".”h]”hX7  When any event or tracer is enabled, a hook is enabled
in the sched_switch trace point to fill comm cache
with mapped pids and comms. But this may cause some
overhead, and if you only care about pids, and not the
name of the task, disabling this option can lower the
impact of tracing. See â€œsaved_cmdlinesâ€.”…””}”(hjâ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M+hjß  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÍ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M0hjq  ubj“  )”}”(hŒ»record-tgid
When any event or tracer is enabled, a hook is enabled
in the sched_switch trace point to fill the cache of
mapped Thread Group IDs (TGID) mapping to pids. See
"saved_tgids".
”h]”(j™  )”}”(hŒrecord-tgid”h]”hŒrecord-tgid”…””}”(hj    h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M6hjü  ubj©  )”}”(hhh]”hÌ)”}”(hŒ®When any event or tracer is enabled, a hook is enabled
in the sched_switch trace point to fill the cache of
mapped Thread Group IDs (TGID) mapping to pids. See
"saved_tgids".”h]”hŒ²When any event or tracer is enabled, a hook is enabled
in the sched_switch trace point to fill the cache of
mapped Thread Group IDs (TGID) mapping to pids. See
â€œsaved_tgidsâ€.”…””}”(hj   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M3hj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjü  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M6hjq  ubj“  )”}”(hŒæoverwrite
This controls what happens when the trace buffer is
full. If "1" (default), the oldest events are
discarded and overwritten. If "0", then the newest
events are discarded.
(see per_cpu/cpu0/stats for overrun and dropped)
”h]”(j™  )”}”(hŒ	overwrite”h]”hŒ	overwrite”…””}”(hj/   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M=hj+   ubj©  )”}”(hhh]”hÌ)”}”(hŒÛThis controls what happens when the trace buffer is
full. If "1" (default), the oldest events are
discarded and overwritten. If "0", then the newest
events are discarded.
(see per_cpu/cpu0/stats for overrun and dropped)”h]”hŒãThis controls what happens when the trace buffer is
full. If â€œ1â€ (default), the oldest events are
discarded and overwritten. If â€œ0â€, then the newest
events are discarded.
(see per_cpu/cpu0/stats for overrun and dropped)”…””}”(hj@   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M9hj=   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj+   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M=hjq  ubj“  )”}”(hŒYdisable_on_free
When the free_buffer is closed, tracing will
stop (tracing_on set to 0).
”h]”(j™  )”}”(hŒdisable_on_free”h]”hŒdisable_on_free”…””}”(hj^   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MAhjZ   ubj©  )”}”(hhh]”hÌ)”}”(hŒHWhen the free_buffer is closed, tracing will
stop (tracing_on set to 0).”h]”hŒHWhen the free_buffer is closed, tracing will
stop (tracing_on set to 0).”…””}”(hjo   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M@hjl   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjZ   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MAhjq  ubj“  )”}”(hXe  irq-info
Shows the interrupt, preempt count, need resched data.
When disabled, the trace looks like::

        # tracer: function
        #
        # entries-in-buffer/entries-written: 144405/9452052   #P:4
        #
        #           TASK-PID   CPU#      TIMESTAMP  FUNCTION
        #              | |       |          |         |
                  <idle>-0     [002]  23636.756054: ttwu_do_activate.constprop.89 <-try_to_wake_up
                  <idle>-0     [002]  23636.756054: activate_task <-ttwu_do_activate.constprop.89
                  <idle>-0     [002]  23636.756055: enqueue_task <-activate_task

”h]”(j™  )”}”(hŒirq-info”h]”hŒirq-info”…””}”(hj   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MPhj‰   ubj©  )”}”(hhh]”(hÌ)”}”(hŒ\Shows the interrupt, preempt count, need resched data.
When disabled, the trace looks like::”h]”hŒ[Shows the interrupt, preempt count, need resched data.
When disabled, the trace looks like:”…””}”(hjž   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MDhj›   ubj´  )”}”(hX´  # tracer: function
#
# entries-in-buffer/entries-written: 144405/9452052   #P:4
#
#           TASK-PID   CPU#      TIMESTAMP  FUNCTION
#              | |       |          |         |
          <idle>-0     [002]  23636.756054: ttwu_do_activate.constprop.89 <-try_to_wake_up
          <idle>-0     [002]  23636.756054: activate_task <-ttwu_do_activate.constprop.89
          <idle>-0     [002]  23636.756055: enqueue_task <-activate_task”h]”hX´  # tracer: function
#
# entries-in-buffer/entries-written: 144405/9452052   #P:4
#
#           TASK-PID   CPU#      TIMESTAMP  FUNCTION
#              | |       |          |         |
          <idle>-0     [002]  23636.756054: ttwu_do_activate.constprop.89 <-try_to_wake_up
          <idle>-0     [002]  23636.756054: activate_task <-ttwu_do_activate.constprop.89
          <idle>-0     [002]  23636.756055: enqueue_task <-activate_task”…””}”hj¬   sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MGhj›   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj‰   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MPhjq  ubj“  )”}”(hŒ€markers
When set, the trace_marker is writable (only by root).
When disabled, the trace_marker will error with EINVAL
on write.
”h]”(j™  )”}”(hŒmarkers”h]”hŒmarkers”…””}”(hjÊ   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MUhjÆ   ubj©  )”}”(hhh]”hÌ)”}”(hŒwWhen set, the trace_marker is writable (only by root).
When disabled, the trace_marker will error with EINVAL
on write.”h]”hŒwWhen set, the trace_marker is writable (only by root).
When disabled, the trace_marker will error with EINVAL
on write.”…””}”(hjÛ   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MShjØ   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÆ   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MUhjq  ubj“  )”}”(hX(  event-fork
When set, tasks with PIDs listed in set_event_pid will have
the PIDs of their children added to set_event_pid when those
tasks fork. Also, when tasks with PIDs in set_event_pid exit,
their PIDs will be removed from the file.

This affects PIDs listed in set_event_notrace_pid as well.
”h]”(j™  )”}”(hŒ
event-fork”h]”hŒ
event-fork”…””}”(hjù   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M]hjõ   ubj©  )”}”(hhh]”(hÌ)”}”(hŒàWhen set, tasks with PIDs listed in set_event_pid will have
the PIDs of their children added to set_event_pid when those
tasks fork. Also, when tasks with PIDs in set_event_pid exit,
their PIDs will be removed from the file.”h]”hŒàWhen set, tasks with PIDs listed in set_event_pid will have
the PIDs of their children added to set_event_pid when those
tasks fork. Also, when tasks with PIDs in set_event_pid exit,
their PIDs will be removed from the file.”…””}”(hj
!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MXhj!  ubhÌ)”}”(hŒ:This affects PIDs listed in set_event_notrace_pid as well.”h]”hŒ:This affects PIDs listed in set_event_notrace_pid as well.”…””}”(hj!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M]hj!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjõ   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M]hjq  ubj“  )”}”(hŒöfunction-trace
The latency tracers will enable function tracing
if this option is enabled (default it is). When
it is disabled, the latency tracers do not trace
functions. This keeps the overhead of the tracer down
when performing latency tests.
”h]”(j™  )”}”(hŒfunction-trace”h]”hŒfunction-trace”…””}”(hj6!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mdhj2!  ubj©  )”}”(hhh]”hÌ)”}”(hŒæThe latency tracers will enable function tracing
if this option is enabled (default it is). When
it is disabled, the latency tracers do not trace
functions. This keeps the overhead of the tracer down
when performing latency tests.”h]”hŒæThe latency tracers will enable function tracing
if this option is enabled (default it is). When
it is disabled, the latency tracers do not trace
functions. This keeps the overhead of the tracer down
when performing latency tests.”…””}”(hjG!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M`hjD!  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj2!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mdhjq  ubj“  )”}”(hX(  function-fork
When set, tasks with PIDs listed in set_ftrace_pid will
have the PIDs of their children added to set_ftrace_pid
when those tasks fork. Also, when tasks with PIDs in
set_ftrace_pid exit, their PIDs will be removed from the
file.

This affects PIDs in set_ftrace_notrace_pid as well.
”h]”(j™  )”}”(hŒfunction-fork”h]”hŒfunction-fork”…””}”(hje!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mmhja!  ubj©  )”}”(hhh]”(hÌ)”}”(hŒãWhen set, tasks with PIDs listed in set_ftrace_pid will
have the PIDs of their children added to set_ftrace_pid
when those tasks fork. Also, when tasks with PIDs in
set_ftrace_pid exit, their PIDs will be removed from the
file.”h]”hŒãWhen set, tasks with PIDs listed in set_ftrace_pid will
have the PIDs of their children added to set_ftrace_pid
when those tasks fork. Also, when tasks with PIDs in
set_ftrace_pid exit, their PIDs will be removed from the
file.”…””}”(hjv!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mghjs!  ubhÌ)”}”(hŒ4This affects PIDs in set_ftrace_notrace_pid as well.”h]”hŒ4This affects PIDs in set_ftrace_notrace_pid as well.”…””}”(hj„!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mmhjs!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hja!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mmhjq  ubj“  )”}”(hŒ€display-graph
When set, the latency tracers (irqsoff, wakeup, etc) will
use function graph tracing instead of function tracing.
”h]”(j™  )”}”(hŒdisplay-graph”h]”hŒdisplay-graph”…””}”(hj¢!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mqhjž!  ubj©  )”}”(hhh]”hÌ)”}”(hŒqWhen set, the latency tracers (irqsoff, wakeup, etc) will
use function graph tracing instead of function tracing.”h]”hŒqWhen set, the latency tracers (irqsoff, wakeup, etc) will
use function graph tracing instead of function tracing.”…””}”(hj³!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mphj°!  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjž!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mqhjq  ubj“  )”}”(hŒRstacktrace
When set, a stack trace is recorded after any trace event
is recorded.
”h]”(j™  )”}”(hŒ
stacktrace”h]”hŒ
stacktrace”…””}”(hjÑ!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MuhjÍ!  ubj©  )”}”(hhh]”hÌ)”}”(hŒFWhen set, a stack trace is recorded after any trace event
is recorded.”h]”hŒFWhen set, a stack trace is recorded after any trace event
is recorded.”…””}”(hjâ!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mthjß!  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÍ!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Muhjq  ubj“  )”}”(hŒÄbranch
Enable branch tracing with the tracer. This enables branch
tracer along with the currently set tracer. Enabling this
with the "nop" tracer is the same as just enabling the
"branch" tracer.
”•g      h]”(j™  )”}”(hŒbranch”h]”hŒbranch”…””}”(hj "  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M{hjü!  ubj©  )”}”(hhh]”hÌ)”}”(hŒ¼Enable branch tracing with the tracer. This enables branch
tracer along with the currently set tracer. Enabling this
with the "nop" tracer is the same as just enabling the
"branch" tracer.”h]”hŒÄEnable branch tracing with the tracer. This enables branch
tracer along with the currently set tracer. Enabling this
with the â€œnopâ€ tracer is the same as just enabling the
â€œbranchâ€ tracer.”…””}”(hj"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mxhj"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjü!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M{hjq  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjm  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MŒhjú  h²hubhŒtip”“”)”}”(hŒŠSome tracers have their own options. They only appear in this
file when the tracer is active. They always appear in the
options directory.”h]”hÌ)”}”(hŒŠSome tracers have their own options. They only appear in this
file when the tracer is active. They always appear in the
options directory.”h]”hŒŠSome tracers have their own options. They only appear in this
file when the tracer is active. They always appear in the
options directory.”…””}”(hj="  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M}hj9"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j7"  hjú  h²hh³hÊh´NubhÌ)”}”(hŒ Here are the per tracer options:”h]”hŒ Here are the per tracer options:”…””}”(hjQ"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‚hjú  h²hubhÌ)”}”(hŒOptions for function tracer:”h]”hŒOptions for function tracer:”…””}”(hj_"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M„hjú  h²hubjh  )”}”(hX^  func_stack_trace
      When set, a stack trace is recorded after every
      function that is recorded. NOTE! Limit the functions
      that are recorded before enabling this, with
      "set_ftrace_filter" otherwise the system performance
      will be critically degraded. Remember to disable
      this option before clearing the function filter.
”h]”jŽ  )”}”(hhh]”j“  )”}”(hX:  func_stack_trace
When set, a stack trace is recorded after every
function that is recorded. NOTE! Limit the functions
that are recorded before enabling this, with
"set_ftrace_filter" otherwise the system performance
will be critically degraded. Remember to disable
this option before clearing the function filter.
”h]”(j™  )”}”(hŒfunc_stack_trace”h]”hŒfunc_stack_trace”…””}”(hjx"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MŒhjt"  ubj©  )”}”(hhh]”hÌ)”}”(hX(  When set, a stack trace is recorded after every
function that is recorded. NOTE! Limit the functions
that are recorded before enabling this, with
"set_ftrace_filter" otherwise the system performance
will be critically degraded. Remember to disable
this option before clearing the function filter.”h]”hX,  When set, a stack trace is recorded after every
function that is recorded. NOTE! Limit the functions
that are recorded before enabling this, with
â€œset_ftrace_filterâ€ otherwise the system performance
will be critically degraded. Remember to disable
this option before clearing the function filter.”…””}”(hj‰"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‡hj†"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjt"  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MŒhjq"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjm"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M†hjú  h²hubhÌ)”}”(hŒ"Options for function_graph tracer:”h]”hŒ"Options for function_graph tracer:”…””}”(hj¯"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŽhjú  h²hubjh  )”}”(hXâ
  Since the function_graph tracer has a slightly different output
it has its own options to control what is displayed.

 funcgraph-overrun
       When set, the "overrun" of the graph stack is
       displayed after each function traced. The
       overrun, is when the stack depth of the calls
       is greater than what is reserved for each task.
       Each task has a fixed array of functions to
       trace in the call graph. If the depth of the
       calls exceeds that, the function is not traced.
       The overrun is the number of functions missed
       due to exceeding this array.

 funcgraph-cpu
       When set, the CPU number of the CPU where the trace
       occurred is displayed.

 funcgraph-overhead
       When set, if the function takes longer than
       A certain amount, then a delay marker is
       displayed. See "delay" above, under the
       header description.

 funcgraph-proc
       Unlike other tracers, the process' command line
       is not displayed by default, but instead only
       when a task is traced in and out during a context
       switch. Enabling this options has the command
       of each process displayed at every line.

 funcgraph-duration
       At the end of each function (the return)
       the duration of the amount of time in the
       function is displayed in microseconds.

 funcgraph-abstime
       When set, the timestamp is displayed at each line.

 funcgraph-irqs
       When disabled, functions that happen inside an
       interrupt will not be traced.

 funcgraph-tail
       When set, the return event will include the function
       that it represents. By default this is off, and
       only a closing curly bracket "}" is displayed for
       the return of a function.

 funcgraph-retval
       When set, the return value of each traced function
       will be printed after an equal sign "=". By default
       this is off.

 funcgraph-retval-hex
       When set, the return value will always be printed
       in hexadecimal format. If the option is not set and
       the return value is an error code, it will be printed
       in signed decimal format; otherwise it will also be
       printed in hexadecimal format. By default, this option
       is off.

 sleep-time
       When running function graph tracer, to include
       the time a task schedules out in its function.
       When enabled, it will account time the task has been
       scheduled out as part of the function call.

 graph-time
       When running function profiler with function graph tracer,
       to include the time to call nested functions. When this is
       not set, the time reported for the function will only
       include the time the function itself executed for, not the
       time for functions that it called.
”h]”(hÌ)”}”(hŒtSince the function_graph tracer has a slightly different output
it has its own options to control what is displayed.”h]”hŒtSince the function_graph tracer has a slightly different output
it has its own options to control what is displayed.”…””}”(hjÁ"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj½"  ubjh  )”}”(hX0
  funcgraph-overrun
      When set, the "overrun" of the graph stack is
      displayed after each function traced. The
      overrun, is when the stack depth of the calls
      is greater than what is reserved for each task.
      Each task has a fixed array of functions to
      trace in the call graph. If the depth of the
      calls exceeds that, the function is not traced.
      The overrun is the number of functions missed
      due to exceeding this array.

funcgraph-cpu
      When set, the CPU number of the CPU where the trace
      occurred is displayed.

funcgraph-overhead
      When set, if the function takes longer than
      A certain amount, then a delay marker is
      displayed. See "delay" above, under the
      header description.

funcgraph-proc
      Unlike other tracers, the process' command line
      is not displayed by default, but instead only
      when a task is traced in and out during a context
      switch. Enabling this options has the command
      of each process displayed at every line.

funcgraph-duration
      At the end of each function (the return)
      the duration of the amount of time in the
      function is displayed in microseconds.

funcgraph-abstime
      When set, the timestamp is displayed at each line.

funcgraph-irqs
      When disabled, functions that happen inside an
      interrupt will not be traced.

funcgraph-tail
      When set, the return event will include the function
      that it represents. By default this is off, and
      only a closing curly bracket "}" is displayed for
      the return of a function.

funcgraph-retval
      When set, the return value of each traced function
      will be printed after an equal sign "=". By default
      this is off.

funcgraph-retval-hex
      When set, the return value will always be printed
      in hexadecimal format. If the option is not set and
      the return value is an error code, it will be printed
      in signed decimal format; otherwise it will also be
      printed in hexadecimal format. By default, this option
      is off.

sleep-time
      When running function graph tracer, to include
      the time a task schedules out in its function.
      When enabled, it will account time the task has been
      scheduled out as part of the function call.

graph-time
      When running function profiler with function graph tracer,
      to include the time to call nested functions. When this is
      not set, the time reported for the function will only
      include the time the function itself executed for, not the
      time for functions that it called.
”h]”jŽ  )”}”(hhh]”(j“  )”}”(hXœ  funcgraph-overrun
When set, the "overrun" of the graph stack is
displayed after each function traced. The
overrun, is when the stack depth of the calls
is greater than what is reserved for each task.
Each task has a fixed array of functions to
trace in the call graph. If the depth of the
calls exceeds that, the function is not traced.
The overrun is the number of functions missed
due to exceeding this array.
”h]”(j™  )”}”(hŒfuncgraph-overrun”h]”hŒfuncgraph-overrun”…””}”(hjÚ"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MœhjÖ"  ubj©  )”}”(hhh]”hÌ)”}”(hX‰  When set, the "overrun" of the graph stack is
displayed after each function traced. The
overrun, is when the stack depth of the calls
is greater than what is reserved for each task.
Each task has a fixed array of functions to
trace in the call graph. If the depth of the
calls exceeds that, the function is not traced.
The overrun is the number of functions missed
due to exceeding this array.”h]”hX  When set, the â€œoverrunâ€ of the graph stack is
displayed after each function traced. The
overrun, is when the stack depth of the calls
is greater than what is reserved for each task.
Each task has a fixed array of functions to
trace in the call graph. If the depth of the
calls exceeds that, the function is not traced.
The overrun is the number of functions missed
due to exceeding this array.”…””}”(hjë"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M”hjè"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÖ"  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MœhjÓ"  ubj“  )”}”(hŒYfuncgraph-cpu
When set, the CPU number of the CPU where the trace
occurred is displayed.
”h]”(j™  )”}”(hŒfuncgraph-cpu”h]”hŒfuncgraph-cpu”…””}”(hj	#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M hj#  ubj©  )”}”(hhh]”hÌ)”}”(hŒJWhen set, the CPU number of the CPU where the trace
occurred is displayed.”h]”hŒJWhen set, the CPU number of the CPU where the trace
occurred is displayed.”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŸhj#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj#  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M hjÓ"  ubj“  )”}”(hŒ¤funcgraph-overhead
When set, if the function takes longer than
A certain amount, then a delay marker is
displayed. See "delay" above, under the
header description.
”h]”(j™  )”}”(hŒfuncgraph-overhead”h]”hŒfuncgraph-overhead”…””}”(hj8#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M¦hj4#  ubj©  )”}”(hhh]”hÌ)”}”(hŒWhen set, if the function takes longer than
A certain amount, then a delay marker is
displayed. See "delay" above, under the
header description.”h]”hŒ”When set, if the function takes longer than
A certain amount, then a delay marker is
displayed. See â€œdelayâ€ above, under the
header description.”…””}”(hjI#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M£hjF#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj4#  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M¦hjÓ"  ubj“  )”}”(hŒöfuncgraph-proc
Unlike other tracers, the process' command line
is not displayed by default, but instead only
when a task is traced in and out during a context
switch. Enabling this options has the command
of each process displayed at every line.
”h]”(j™  )”}”(hŒfuncgraph-proc”h]”hŒfuncgraph-proc”…””}”(hjg#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M­hjc#  ubj©  )”}”(hhh]”hÌ)”}”(hŒæUnlike other tracers, the process' command line
is not displayed by default, but instead only
when a task is traced in and out during a context
switch. Enabling this options has the command
of each process displayed at every line.”h]”hŒèUnlike other tracers, the processâ€™ command line
is not displayed by default, but instead only
when a task is traced in and out during a context
switch. Enabling this options has the command
of each process displayed at every line.”…””}”(hjx#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M©hju#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjc#  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M­hjÓ"  ubj“  )”}”(hŒfuncgraph-duration
At the end of each function (the return)
the duration of the amount of time in the
function is displayed in microseconds.
”h]”(j™  )”}”(hŒfuncgraph-duration”h]”hŒfuncgraph-duration”…””}”(hj–#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M²hj’#  ubj©  )”}”(hhh]”hÌ)”}”(hŒyAt the end of each function (the return)
the duration of the amount of time in the
function is displayed in microseconds.”h]”hŒyAt the end of each function (the return)
the duration of the amount of time in the
function is displayed in microseconds.”…””}”(hj§#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M°hj¤#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj’#  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M²hjÓ"  ubj“  )”}”(hŒEfuncgraph-abstime
When set, the timestamp is displayed at each line.
”h]”(j™  )”}”(hŒfuncgraph-abstime”h]”hŒfuncgraph-abstime”…””}”(hjÅ#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MµhjÁ#  ubj©  )”}”(hhh]”hÌ)”}”(hŒ2When set, the timestamp is displayed at each line.”h]”hŒ2When set, the timestamp is displayed at each line.”…””}”(hjÖ#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MµhjÓ#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÁ#  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MµhjÓ"  ubj“  )”}”(hŒ\funcgraph-irqs
When disabled, functions that happen inside an
interrupt will not be traced.
”h]”(j™  )”}”(hŒfuncgraph-irqs”h]”hŒfuncgraph-irqs”…””}”(hjô#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M¹hjð#  ubj©  )”}”(hhh]”hÌ)”}”(hŒLWhen disabled, functions that happen inside an
interrupt will not be traced.”h]”hŒLWhen disabled, functions that happen inside an
interrupt will not be traced.”…””}”(hj$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¸hj$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjð#  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M¹hjÓ"  ubj“  )”}”(hŒÀfuncgraph-tail
When set, the return event will include the function
that it represents. By default this is off, and
only a closing curly bracket "}" is displayed for
the return of a function.
”h]”(j™  )”}”(hŒfuncgraph-tail”h]”hŒfuncgraph-tail”…””}”(hj#$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M¿hj$  ubj©  )”}”(hhh]”hÌ)”}”(hŒ°When set, the return event will include the function
that it represents. By default this is off, and
only a closing curly bracket "}" is displayed for
the return of a function.”h]”hŒ´When set, the return event will include the function
that it represents. By default this is off, and
only a closing curly bracket â€œ}â€ is displayed for
the return of a function.”…””}”(hj4$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¼hj1$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj$  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M¿hjÓ"  ubj“  )”}”(hŒ…funcgraph-retval
When set, the return value of each traced function
will be printed after an equal sign "=". By default
this is off.
”h]”(j™  )”}”(hŒfuncgraph-retval”h]”hŒfuncgraph-retval”…””}”(hjR$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÄhjN$  ubj©  )”}”(hhh]”hÌ)”}”(hŒsWhen set, the return value of each traced function
will be printed after an equal sign "=". By default
this is off.”h]”hŒwWhen set, the return value of each traced function
will be printed after an equal sign â€œ=â€. By default
this is off.”…””}”(hjc$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÂhj`$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjN$  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÄhjÓ"  ubj“  )”}”(hX$  funcgraph-retval-hex
When set, the return value will always be printed
in hexadecimal format. If the option is not set and
the return value is an error code, it will be printed
in signed decimal format; otherwise it will also be
printed in hexadecimal format. By default, this option
is off.
”h]”(j™  )”}”(hŒfuncgraph-retval-hex”h]”hŒfuncgraph-retval-hex”…””}”(hj$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÌhj}$  ubj©  )”}”(hhh]”hÌ)”}”(hX  When set, the return value will always be printed
in hexadecimal format. If the option is not set and
the return value is an error code, it will be printed
in signed decimal format; otherwise it will also be
printed in hexadecimal format. By default, this option
is off.”h]”hX  When set, the return value will always be printed
in hexadecimal format. If the option is not set and
the return value is an error code, it will be printed
in signed decimal format; otherwise it will also be
printed in hexadecimal format. By default, this option
is off.”…””}”(hj’$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÇhj$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj}$  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÌhjÓ"  ubj“  )”}”(hŒÊsleep-time
When running function graph tracer, to include
the time a task schedules out in its function.
When enabled, it will account time the task has been
scheduled out as part of the function call.
”h]”(j™  )”}”(hŒ
sleep-time”h]”hŒ
sleep-time”…””}”(hj°$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÒhj¬$  ubj©  )”}”(hhh]”hÌ)”}”(hŒ¾When running function graph tracer, to include
the time a task schedules out in its function.
When enabled, it will account time the task has been
scheduled out as part of the function call.”h]”hŒ¾When running function graph tracer, to include
the time a task schedules out in its function.
When enabled, it will account time the task has been
scheduled out as part of the function call.”…””}”(hjÁ$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÏhj¾$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj¬$  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÒhjÓ"  ubj“  )”}”(hX  graph-time
When running function profiler with function graph tracer,
to include the time to call nested functions. When this is
not set, the time reported for the function will only
include the time the function itself executed for, not the
time for functions that it called.
”h]”(j™  )”}”(hŒ
graph-time”h]”hŒ
graph-time”…””}”(hjß$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MÙhjÛ$  ubj©  )”}”(hhh]”hÌ)”}”(hX	  When running function profiler with function graph tracer,
to include the time to call nested functions. When this is
not set, the time reported for the function will only
include the time the function itself executed for, not the
time for functions that it called.”h]”hX	  When running function profiler with function graph tracer,
to include the time to call nested functions. When this is
not set, the time reported for the function will only
include the time the function itself executed for, not the
time for functions that it called.”…””}”(hjð$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÕhjí$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjÛ$  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MÙhjÓ"  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjÏ"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M“hj½"  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhjú  h²hubhÌ)”}”(hŒOptions for blk tracer:”h]”hŒOptions for blk tracer:”…””}”(hj%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÛhjú  h²hubjh  )”}”(hŒ5blk_classic
      Shows a more minimalistic output.

”h]”jŽ  )”}”(hhh]”j“  )”}”(hŒ/blk_classic
Shows a more minimalistic output.

”h]”(j™  )”}”(hŒblk_classic”h]”hŒblk_classic”…””}”(hj5%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mßhj1%  ubj©  )”}”(hhh]”hÌ)”}”(hŒ!Shows a more minimalistic output.”h]”hŒ!Shows a more minimalistic output.”…””}”(hjF%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÞhjC%  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj1%  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mßhj.%  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj*%  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÝhjú  h²hubeh}”(h]”Œtrace-options”ah ]”h"]”Œtrace_options”ah$]”h&]”uh1hµhh·h²hh³hÊh´M]ubh¶)”}”(hhh]”(h»)”}”(hŒirqsoff”h]”hŒirqsoff”…””}”(hjw%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjt%  h²hh³hÊh´MâubhÌ)”}”(hX  When interrupts are disabled, the CPU can not react to any other
external event (besides NMIs and SMIs). This prevents the timer
interrupt from triggering or the mouse interrupt from letting
the kernel know of a new mouse event. The result is a latency
with the reaction time.”h]”hX  When interrupts are disabled, the CPU can not react to any other
external event (besides NMIs and SMIs). This prevents the timer
interrupt from triggering or the mouse interrupt from letting
the kernel know of a new mouse event. The result is a latency
with the reaction time.”…””}”(hj…%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mähjt%  h²hubhÌ)”}”(hX  The irqsoff tracer tracks the time for which interrupts are
disabled. When a new maximum latency is hit, the tracer saves
the trace leading up to that latency point so that every time a
new maximum is reached, the old saved trace is discarded and the
new trace is saved.”h]”hX  The irqsoff tracer tracks the time for which interrupts are
disabled. When a new maximum latency is hit, the tracer saves
the trace leading up to that latency point so that every time a
new maximum is reached, the old saved trace is discarded and the
new trace is saved.”…””}”(hj“%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mêhjt%  h²hubhÌ)”}”(hŒKTo reset the maximum, echo 0 into tracing_max_latency. Here is
an example::”h]”hŒJTo reset the maximum, echo 0 into tracing_max_latency. Here is
an example:”…””}”(hj¡%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mðhjt%  h²hubj´  )”}”(hX  # echo 0 > options/function-trace
# echo irqsoff > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# ls -ltr
[...]
# echo 0 > tracing_on
# cat trace
# tracer: irqsoff
#
# irqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 16 us, #4/4, CPU#0 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: swapper/0-0 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: run_timer_softirq
#  => ended at:   run_timer_softirq
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       0d.s2    0us+: _raw_spin_lock_irq <-run_timer_softirq
  <idle>-0       0dNs3   17us : _raw_spin_unlock_irq <-run_timer_softirq
  <idle>-0       0dNs3   17us+: trace_hardirqs_on <-run_timer_softirq
  <idle>-0       0dNs3   25us : <stack trace>
 => _raw_spin_unlock_irq
 => run_timer_softirq
 => __do_softirq
 => call_softirq
 => do_softirq
 => irq_exit
 => smp_apic_timer_interrupt
 => apic_timer_interrupt
 => rcu_idle_exit
 => cpu_idle
 => rest_init
 => start_kernel
 => x86_64_start_reservations
 => x86_64_start_kernel”h]”hX  # echo 0 > options/function-trace
# echo irqsoff > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# ls -ltr
[...]
# echo 0 > tracing_on
# cat trace
# tracer: irqsoff
#
# irqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 16 us, #4/4, CPU#0 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: swapper/0-0 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: run_timer_softirq
#  => ended at:   run_timer_softirq
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       0d.s2    0us+: _raw_spin_lock_irq <-run_timer_softirq
  <idle>-0       0dNs3   17us : _raw_spin_unlock_irq <-run_timer_softirq
  <idle>-0       0dNs3   17us+: trace_hardirqs_on <-run_timer_softirq
  <idle>-0       0dNs3   25us : <stack trace>
 => _raw_spin_unlock_irq
 => run_timer_softirq
 => __do_softirq
 => call_softirq
 => do_softirq
 => irq_exit
 => smp_apic_timer_interrupt
 => apic_timer_interrupt
 => rcu_idle_exit
 => cpu_idle
 => rest_init
 => start_kernel
 => x86_64_start_reservations
 => x86_64_start_kernel”…””}”hj¯%  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Móhjt%  h²hubhÌ)”}”(hXa  Here we see that we had a latency of 16 microseconds (which is
very good). The _raw_spin_lock_irq in run_timer_softirq disabled
interrupts. The difference between the 16 and the displayed
timestamp 25us occurred because the clock was incremented
between the time of recording the max latency and the time of
recording the function that had that latency.”h]”hXa  Here we see that we had a latency of 16 microseconds (which is
very good). The _raw_spin_lock_irq in run_timer_softirq disabled
interrupts. The difference between the 16 and the displayed
timestamp 25us occurred because the clock was incremented
between the time of recording the max latency and the time of
recording the function that had that latency.”…””}”(hj½%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M"hjt%  h²hubhÌ)”}”(hŒjNote the above example had function-trace not set. If we set
function-trace, we get a much larger output::”h]”hŒiNote the above example had function-trace not set. If we set
function-trace, we get a much larger output:”…””}”(hjË%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M)hjt%  h²hubj´  )”}”(hX
  with echo 1 > options/function-trace

 # tracer: irqsoff
 #
 # irqsoff latency trace v1.1.5 on 3.8.0-test+
 # --------------------------------------------------------------------
 # latency: 71 us, #168/168, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
 #    -----------------
 #    | task: bash-2042 (uid:0 nice:0 policy:0 rt_prio:0)
 #    -----------------
 #  => started at: ata_scsi_queuecmd
 #  => ended at:   ata_scsi_queuecmd
 #
 #
 #                  _------=> CPU#
 #                 / _-----=> irqs-off
 #                | / _----=> need-resched
 #                || / _---=> hardirq/softirq
 #                ||| / _--=> preempt-depth
 #                |||| /     delay
 #  cmd     pid   ||||| time  |   caller
 #     \   /      |||||  \    |   /
     bash-2042    3d...    0us : _raw_spin_lock_irqsave <-ata_scsi_queuecmd
     bash-2042    3d...    0us : add_preempt_count <-_raw_spin_lock_irqsave
     bash-2042    3d..1    1us : ata_scsi_find_dev <-ata_scsi_queuecmd
     bash-2042    3d..1    1us : __ata_scsi_find_dev <-ata_scsi_find_dev
     bash-2042    3d..1    2us : ata_find_dev.part.14 <-__ata_scsi_find_dev
     bash-2042    3d..1    2us : ata_qc_new_init <-__ata_scsi_queuecmd
     bash-2042    3d..1    3us : ata_sg_init <-__ata_scsi_queuecmd
     bash-2042    3d..1    4us : ata_scsi_rw_xlat <-__ata_scsi_queuecmd
     bash-2042    3d..1    4us : ata_build_rw_tf <-ata_scsi_rw_xlat
 [...]
     bash-2042    3d..1   67us : delay_tsc <-__delay
     bash-2042    3d..1   67us : add_preempt_count <-delay_tsc
     bash-2042    3d..2   67us : sub_preempt_count <-delay_tsc
     bash-2042    3d..1   67us : add_preempt_count <-delay_tsc
     bash-2042    3d..2   68us : sub_preempt_count <-delay_tsc
     bash-2042    3d..1   68us+: ata_bmdma_start <-ata_bmdma_qc_issue
     bash-2042    3d..1   71us : _raw_spin_unlock_irqrestore <-ata_scsi_queuecmd
     bash-2042    3d..1   71us : _raw_spin_unlock_irqrestore <-ata_scsi_queuecmd
     bash-2042    3d..1   72us+: trace_hardirqs_on <-ata_scsi_queuecmd
     bash-2042    3d..1  120us : <stack trace>
  => _raw_spin_unlock_irqrestore
  => ata_scsi_queuecmd
  => scsi_dispatch_cmd
  => scsi_request_fn
  => __blk_run_queue_uncond
  => __blk_run_queue
  => blk_queue_bio
  => submit_bio_noacct
  => submit_bio
  => bh_submit
  => __ext3_get_inode_loc
  => ext3_iget
  => ext3_lookup
  => lookup_real
  => __lookup_hash
  => walk_component
  => lookup_last
  => path_lookupat
  => filename_lookup
  => user_path_at_empty
  => user_path_at
  => vfs_fstatat
  => vfs_stat
  => sys_newstat
  => system_call_fastpath”h]”hX
  with echo 1 > options/function-trace

 # tracer: irqsoff
 #
 # irqsoff latency trace v1.1.5 on 3.8.0-test+
 # --------------------------------------------------------------------
 # latency: 71 us, #168/168, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
 #    -----------------
 #    | task: bash-2042 (uid:0 nice:0 policy:0 rt_prio:0)
 #    -----------------
 #  => started at: ata_scsi_queuecmd
 #  => ended at:   ata_scsi_queuecmd
 #
 #
 #                  _------=> CPU#
 #                 / _-----=> irqs-off
 #                | / _----=> need-resched
 #                || / _---=> hardirq/softirq
 #                ||| / _--=> preempt-depth
 #                |||| /     delay
 #  cmd     pid   ||||| time  |   caller
 #     \   /      |||||  \    |   /
     bash-2042    3d...    0us : _raw_spin_lock_irqsave <-ata_scsi_queuecmd
     bash-2042    3d...    0us : add_preempt_count <-_raw_spin_lock_irqsave
     bash-2042    3d..1    1us : ata_scsi_find_dev <-ata_scsi_queuecmd
     bash-2042    3d..1    1us : __ata_scsi_find_dev <-ata_scsi_find_dev
     bash-2042    3d..1    2us : ata_find_dev.part.14 <-__ata_scsi_find_dev
     bash-2042    3d..1    2us : ata_qc_new_init <-__ata_scsi_queuecmd
     bash-2042    3d..1    3us : ata_sg_init <-__ata_scsi_queuecmd
     bash-2042    3d..1    4us : ata_scsi_rw_xlat <-__ata_scsi_queuecmd
     bash-2042    3d..1    4us : ata_build_rw_tf <-ata_scsi_rw_xlat
 [...]
     bash-2042    3d..1   67us : delay_tsc <-__delay
     bash-2042    3d..1   67us : add_preempt_count <-delay_tsc
     bash-2042    3d..2   67us : sub_preempt_count <-delay_tsc
     bash-2042    3d..1   67us : add_preempt_count <-delay_tsc
     bash-2042    3d..2   68us : sub_preempt_count <-delay_tsc
     bash-2042    3d..1   68us+: ata_bmdma_start <-ata_bmdma_qc_issue
     bash-2042    3d..1   71us : _raw_spin_unlock_irqrestore <-ata_scsi_queuecmd
     bash-2042    3d..1   71us : _raw_spin_unlock_irqrestore <-ata_scsi_queuecmd
     bash-2042    3d..1   72us+: trace_hardirqs_on <-ata_scsi_queuecmd
     bash-2042    3d..1  120us : <stack trace>
  => _raw_spin_unlock_irqrestore
  => ata_scsi_queuecmd
  => scsi_dispatch_cmd
  => scsi_request_fn
  => __blk_run_queue_uncond
  => __blk_run_queue
  => blk_queue_bio
  => submit_bio_noacct
  => submit_bio
  => bh_submit
  => __ext3_get_inode_loc
  => ext3_iget
  => ext3_lookup
  => lookup_real
  => __lookup_hash
  => walk_component
  => lookup_last
  => path_lookupat
  => filename_lookup
  => user_path_at_empty
  => user_path_at
  => vfs_fstatat
  => vfs_stat
  => sys_newstat
  => system_call_fastpath”…””}”hjÙ%  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M,hjt%  h²hubhÌ)”}”(hX0  Here we traced a 71 microsecond latency. But we also see all the
functions that were called during that time. Note that by
enabling function tracing, we incur an added overhead. This
overhead may extend the latency times. But nevertheless, this
trace has provided some very helpful debugging information.”h]”hX0  Here we traced a 71 microsecond latency. But we also see all the
functions that were called during that time. Note that by
enabling function tracing, we incur an added overhead. This
overhead may extend the latency times. But nevertheless, this
trace has provided some very helpful debugging information.”…””}”(hjç%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mqhjt%  h²hubhÌ)”}”(hŒYIf we prefer function graph output instead of function, we can set
display-graph option::”h]”hŒXIf we prefer function graph output instead of function, we can set
display-graph option:”…””}”(hjõ%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mwhjt%  h²hubj´  )”}”(hX	  with echo 1 > options/display-graph

 # tracer: irqsoff
 #
 # irqsoff latency trace v1.1.5 on 4.20.0-rc6+
 # --------------------------------------------------------------------
 # latency: 3751 us, #274/274, CPU#0 | (M:desktop VP:0, KP:0, SP:0 HP:0 #P:4)
 #    -----------------
 #    | task: bash-1507 (uid:0 nice:0 policy:0 rt_prio:0)
 #    -----------------
 #  => started at: free_debug_processing
 #  => ended at:   return_to_handler
 #
 #
 #                                       _-----=> irqs-off
 #                                      / _----=> need-resched
 #                                     | / _---=> hardirq/softirq
 #                                     || / _--=> preempt-depth
 #                                     ||| /
 #   REL TIME      CPU  TASK/PID       ||||     DURATION                  FUNCTION CALLS
 #      |          |     |    |        ||||      |   |                     |   |   |   |
         0 us |   0)   bash-1507    |  d... |   0.000 us    |  _raw_spin_lock_irqsave();
         0 us |   0)   bash-1507    |  d..1 |   0.378 us    |    do_raw_spin_trylock();
         1 us |   0)   bash-1507    |  d..2 |               |    set_track() {
         2 us |   0)   bash-1507    |  d..2 |               |      save_stack_trace() {
         2 us |   0)   bash-1507    |  d..2 |               |        __save_stack_trace() {
         3 us |   0)   bash-1507    |  d..2 |               |          __unwind_start() {
         3 us |   0)   bash-1507    |  d..2 |               |            get_stack_info() {
         3 us |   0)   bash-1507    |  d..2 |   0.351 us    |              in_task_stack();
         4 us |   0)   bash-1507    |  d..2 |   1.107 us    |            }
 [...]
      3750 us |   0)   bash-1507    |  d..1 |   0.516 us    |      do_raw_spin_unlock();
      3750 us |   0)   bash-1507    |  d..1 |   0.000 us    |  _raw_spin_unlock_irqrestore();
      3764 us |   0)   bash-1507    |  d..1 |   0.000 us    |  tracer_hardirqs_on();
     bash-1507    0d..1 3792us : <stack trace>
  => free_debug_processing
  => __slab_free
  => kmem_cache_free
  => vm_area_free
  => remove_vma
  => exit_mmap
  => mmput
  => begin_new_exec
  => load_elf_binary
  => search_binary_handler
  => __do_execve_file.isra.32
  => __x64_sys_execve
  => do_syscall_64
  => entry_SYSCALL_64_after_hwframe”h]”hX	  with echo 1 > options/display-graph

 # tracer: irqsoff
 #
 # irqsoff latency trace v1.1.5 on 4.20.0-rc6+
 # --------------------------------------------------------------------
 # latency: 3751 us, #274/274, CPU#0 | (M:desktop VP:0, KP:0, SP:0 HP:0 #P:4)
 #    -----------------
 #    | task: bash-1507 (uid:0 nice:0 policy:0 rt_prio:0)
 #    -----------------
 #  => started at: free_debug_processing
 #  => ended at:   return_to_handler
 #
 #
 #                                       _-----=> irqs-off
 #                                      / _----=> need-resched
 #                                     | / _---=> hardirq/softirq
 #                                     || / _--=> preempt-depth
 #                                     ||| /
 #   REL TIME      CPU  TASK/PID       ||||     DURATION                  FUNCTION CALLS
 #      |          |     |    |        ||||      |   |                     |   |   |   |
         0 us |   0)   bash-1507    |  d... |   0.000 us    |  _raw_spin_lock_irqsave();
         0 us |   0)   bash-1507    |  d..1 |   0.378 us    |    do_raw_spin_trylock();
         1 us |   0)   bash-1507    |  d..2 |               |    set_track() {
         2 us |   0)   bash-1507    |  d..2 |               |      save_stack_trace() {
         2 us |   0)   bash-1507    |  d..2 |               |        __save_stack_trace() {
         3 us |   0)   bash-1507    |  d..2 |               |          __unwind_start() {
         3 us |   0)   bash-1507    |  d..2 |               |            get_stack_info() {
         3 us |   0)   bash-1507    |  d..2 |   0.351 us    |              in_task_stack();
         4 us |   0)   bash-1507    |  d..2 |   1.107 us    |            }
 [...]
      3750 us |   0)   bash-1507    |  d..1 |   0.516 us    |      do_raw_spin_unlock();
      3750 us |   0)   bash-1507    |  d..1 |   0.000 us    |  _raw_spin_unlock_irqrestore();
      3764 us |   0)   bash-1507    |  d..1 |   0.000 us    |  tracer_hardirqs_on();
     bash-1507    0d..1 3792us : <stack trace>
  => free_debug_processing
  => __slab_free
  => kmem_cache_free
  => vm_area_free
  => remove_vma
  => exit_mmap
  => mmput
  => begin_new_exec
  => load_elf_binary
  => search_binary_handler
  => __do_execve_file.isra.32
  => __x64_sys_execve
  => do_syscall_64
  => entry_SYSCALL_64_after_hwframe”…””}”hj&  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mzhjt%  h²hubeh}”(h]”Œirqsoff”ah ]”h"]”Œirqsoff”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mâubh¶)”}”(hhh]”(h»)”}”(hŒ
preemptoff”h]”hŒ
preemptoff”…””}”(hj&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj&  h²hh³hÊh´M­ubhÌ)”}”(hŒ×When preemption is disabled, we may be able to receive
interrupts but the task cannot be preempted and a higher
priority task must wait for preemption to be enabled again
before it can preempt a lower priority task.”h]”hŒ×When preemption is disabled, we may be able to receive
interrupts but the task cannot be preempted and a higher
priority task must wait for preemption to be enabled again
before it can preempt a lower priority task.”…””}”(hj*&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¯hj&  h²hubhÌ)”}”(hŒàThe preemptoff tracer traces the places that disable preemption.
Like the irqsoff tracer, it records the maximum latency for
which preemption was disabled. The control of preemptoff tracer
is much like the irqsoff tracer.
::”h]”hŒÝThe preemptoff tracer traces the places that disable preemption.
Like the irqsoff tracer, it records the maximum latency for
which preemption was disabled. The control of preemptoff tracer
is much like the irqsoff tracer.”…””}”(hj8&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M´hj&  h²hubj´  )”}”(hXb  # echo 0 > options/function-trace
# echo preemptoff > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# ls -ltr
[...]
# echo 0 > tracing_on
# cat trace
# tracer: preemptoff
#
# preemptoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 46 us, #4/4, CPU#1 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sshd-1991 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: do_IRQ
#  => ended at:   do_IRQ
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
    sshd-1991    1d.h.    0us+: irq_enter <-do_IRQ
    sshd-1991    1d..1   46us : irq_exit <-do_IRQ
    sshd-1991    1d..1   47us+: trace_preempt_on <-do_IRQ
    sshd-1991    1d..1   52us : <stack trace>
 => sub_preempt_count
 => irq_exit
 => do_IRQ
 => ret_from_intr”h]”hXb  # echo 0 > options/function-trace
# echo preemptoff > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# ls -ltr
[...]
# echo 0 > tracing_on
# cat trace
# tracer: preemptoff
#
# preemptoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 46 us, #4/4, CPU#1 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sshd-1991 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: do_IRQ
#  => ended at:   do_IRQ
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
    sshd-1991    1d.h.    0us+: irq_enter <-do_IRQ
    sshd-1991    1d..1   46us : irq_exit <-do_IRQ
    sshd-1991    1d..1   47us+: trace_preempt_on <-do_IRQ
    sshd-1991    1d..1   52us : <stack trace>
 => sub_preempt_count
 => irq_exit
 => do_IRQ
 => ret_from_intr”…””}”hjF&  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mºhj&  h²hubhÌ)”}”(hXI  This has some more changes. Preemption was disabled when an
interrupt came in (notice the 'h'), and was enabled on exit.
But we also see that interrupts have been disabled when entering
the preempt off section and leaving it (the 'd'). We do not know if
interrupts were enabled in the mean time or shortly after this
was over.
::”h]”hXN  This has some more changes. Preemption was disabled when an
interrupt came in (notice the â€˜hâ€™), and was enabled on exit.
But we also see that interrupts have been disabled when entering
the preempt off section and leaving it (the â€˜dâ€™). We do not know if
interrupts were enabled in the mean time or shortly after this
was over.”…””}”(hjT&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Màhj&  h²hubj´  )”}”(hX¢  # tracer: preemptoff
#
# preemptoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 83 us, #241/241, CPU#1 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: bash-1994 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: wake_up_new_task
#  => ended at:   task_rq_unlock
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
    bash-1994    1d..1    0us : _raw_spin_lock_irqsave <-wake_up_new_task
    bash-1994    1d..1    0us : select_task_rq_fair <-select_task_rq
    bash-1994    1d..1    1us : __rcu_read_lock <-select_task_rq_fair
    bash-1994    1d..1    1us : source_load <-select_task_rq_fair
    bash-1994    1d..1    1us : source_load <-select_task_rq_fair
[...]
    bash-1994    1d..1   12us : irq_enter <-smp_apic_timer_interrupt
    bash-1994    1d..1   12us : rcu_irq_enter <-irq_enter
    bash-1994    1d..1   13us : add_preempt_count <-irq_enter
    bash-1994    1d.h1   13us : exit_idle <-smp_apic_timer_interrupt
    bash-1994    1d.h1   13us : hrtimer_interrupt <-smp_apic_timer_interrupt
    bash-1994    1d.h1   13us : _raw_spin_lock <-hrtimer_interrupt
    bash-1994    1d.h1   14us : add_preempt_count <-_raw_spin_lock
    bash-1994    1d.h2   14us : ktime_get_update_offsets <-hrtimer_interrupt
[...]
    bash-1994    1d.h1   35us : lapic_next_event <-clockevents_program_event
    bash-1994    1d.h1   35us : irq_exit <-smp_apic_timer_interrupt
    bash-1994    1d.h1   36us : sub_preempt_count <-irq_exit
    bash-1994    1d..2   36us : do_softirq <-irq_exit
    bash-1994    1d..2   36us : __do_softirq <-call_softirq
    bash-1994    1d..2   36us : __local_bh_disable <-__do_softirq
    bash-1994    1d.s2   37us : add_preempt_count <-_raw_spin_lock_irq
    bash-1994    1d.s3   38us : _raw_spin_unlock <-run_timer_softirq
    bash-1994    1d.s3   39us : sub_preempt_count <-_raw_spin_unlock
    bash-1994    1d.s2   39us : call_timer_fn <-run_timer_softirq
[...]
    bash-1994    1dNs2   81us : cpu_needs_another_gp <-rcu_process_callbacks
    bash-1994    1dNs2   82us : __local_bh_enable <-__do_softirq
    bash-1994    1dNs2   82us : sub_preempt_count <-__local_bh_enable
    bash-1994    1dN.2   82us : idle_cpu <-irq_exit
    bash-1994    1dN.2   83us : rcu_irq_exit <-irq_exit
    bash-1994    1dN.2   83us : sub_preempt_count <-irq_exit
    bash-1994    1.N.1   84us : _raw_spin_unlock_irqrestore <-task_rq_unlock
    bash-1994    1.N.1   84us+: trace_preempt_on <-task_rq_unlock
    bash-1994    1.N.1  104us : <stack trace>
 => sub_preempt_count
 => _raw_spin_unlock_irqrestore
 => task_rq_unlock
 => wake_up_new_task
 => do_fork
 => sys_clone
 => stub_clone”h]”hX¢  # tracer: preemptoff
#
# preemptoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 83 us, #241/241, CPU#1 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: bash-1994 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: wake_up_new_task
#  => ended at:   task_rq_unlock
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
    bash-1994    1d..1    0us : _raw_spin_lock_irqsave <-wake_up_new_task
    bash-1994    1d..1    0us : select_task_rq_fair <-select_task_rq
    bash-1994    1d..1    1us : __rcu_read_lock <-select_task_rq_fair
    bash-1994    1d..1    1us : source_load <-select_task_rq_fair
    bash-1994    1d..1    1us : source_load <-select_task_rq_fair
[...]
    bash-1994    1d..1   12us : irq_enter <-smp_apic_timer_interrupt
    bash-1994    1d..1   12us : rcu_irq_enter <-irq_enter
    bash-1994    1d..1   13us : add_preempt_count <-irq_enter
    bash-1994    1d.h1   13us : exit_idle <-smp_apic_timer_interrupt
    bash-1994    1d.h1   13us : hrtimer_interrupt <-smp_apic_timer_interrupt
    bash-1994    1d.h1   13us : _raw_spin_lock <-hrtimer_interrupt
    bash-1994    1d.h1   14us : add_preempt_count <-_raw_spin_lock
    bash-1994    1d.h2   14us : ktime_get_update_offsets <-hrtimer_interrupt
[...]
    bash-1994    1d.h1   35us : lapic_next_event <-clockevents_program_event
    bash-1994    1d.h1   35us : irq_exit <-smp_apic_timer_interrupt
    bash-1994    1d.h1   36us : sub_preempt_count <-irq_exit
    bash-1994    1d..2   36us : do_softirq <-irq_exit
    bash-1994    1d..2   36us : __do_softirq <-call_softirq
    bash-1994    1d..2   36us : __local_bh_disable <-__do_softirq
    bash-1994    1d.s2   37us : add_preempt_count <-_raw_spin_lock_irq
    bash-1994    1d.s3   38us : _raw_spin_unlock <-run_timer_softirq
    bash-1994    1d.s3   39us : sub_preempt_count <-_raw_spin_unlock
    bash-1994    1d.s2   39us : call_timer_fn <-run_timer_softirq
[...]
    bash-1994    1dNs2   81us : cpu_needs_another_gp <-rcu_process_callbacks
    bash-1994    1dNs2   82us : __local_bh_enable <-__do_softirq
    bash-1994    1dNs2   82us : sub_preempt_count <-__local_bh_enable
    bash-1994    1dN.2   82us : idle_cpu <-irq_exit
    bash-1994    1dN.2   83us : rcu_irq_exit <-irq_exit
    bash-1994    1dN.2   83us : sub_preempt_count <-irq_exit
    bash-1994    1.N.1   84us : _raw_spin_unlock_irqrestore <-task_rq_unlock
    bash-1994    1.N.1   84us+: trace_preempt_on <-task_rq_unlock
    bash-1994    1.N.1  104us : <stack trace>
 => sub_preempt_count
 => _raw_spin_unlock_irqrestore
 => task_rq_unlock
 => wake_up_new_task
 => do_fork
 => sys_clone
 => stub_clone”…””}”hjb&  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mèhj&  h²hubhÌ)”}”(hXd  The above is an example of the preemptoff trace with
function-trace set. Here we see that interrupts were not disabled
the entire time. The irq_enter code lets us know that we entered
an interrupt 'h'. Before that, the functions being traced still
show that it is not in an interrupt, but we can see from the
functions themselves that this is not the case.”h]”hXh  The above is an example of the preemptoff trace with
function-trace set. Here we see that interrupts were not disabled
the entire time. The irq_enter code lets us know that we entered
an interrupt â€˜hâ€™. Before that, the functions being traced still
show that it is not in an interrupt, but we can see from the
functions themselves that this is not the case.”…””}”(hjp&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M(hj&  h²hubeh}”(h]”Œ
preemptoff”ah ]”h"]”Œ
preemptoff”ah$]”h&]”uh1hµhh·h²hh³hÊh´M­ubh¶)”}”(hhh]”(h»)”}”(hŒpreemptirqsoff”h]”hŒpreemptirqsoff”…””}”(hj‰&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj†&  h²hh³hÊh´M0ubhÌ)”}”(hŒÇKnowing the locations that have interrupts disabled or
preemption disabled for the longest times is helpful. But
sometimes we would like to know when either preemption and/or
interrupts are disabled.”h]”hŒÇKnowing the locations that have interrupts disabled or
preemption disabled for the longest times is helpful. But
sometimes we would like to know when either preemption and/or
interrupts are disabled.”…””}”(hj—&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M2hj†&  h²hubhÌ)”}”(hŒConsider the following code::”h]”hŒConsider the following code:”…””}”(hj¥&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M7hj†&  h²hubj´  )”}”(hŒ¿local_irq_disable();
call_function_with_irqs_off();
preempt_disable();
call_function_with_irqs_and_preemption_off();
local_irq_enable();
call_function_with_preemption_off();
preempt_enable();”h]”hŒ¿local_irq_disable();
call_function_with_irqs_off();
preempt_disable();
call_function_with_irqs_and_preemption_off();
local_irq_enable();
call_function_with_preemption_off();
preempt_enable();”…””}”hj³&  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M9hj†&  h²hubhÌ)”}”(hŒ‚The irqsoff tracer will record the total length of
call_function_with_irqs_off() and
call_function_with_irqs_and_preemption_off().”h]”hŒ‚The irqsoff tracer will record the total length of
call_function_with_irqs_off() and
call_function_with_irqs_and_preemption_off().”…””}”(hjÁ&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MAhj†&  h²hubhÌ)”}”(hŒ‹The preemptoff tracer will record the total length of
call_function_with_irqs_and_preemption_off() and
call_function_with_preemption_off().”h]”hŒ‹The preemptoff tracer will record the total length of
call_function_with_irqs_and_preemption_off() and
call_function_with_preemption_off().”…””}”(hjÏ&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MEhj†&  h²hubhÌ)”}”(hŒ¸But neither will trace the time that interrupts and/or
preemption is disabled. This total time is the time that we can
not schedule. To record this time, use the preemptirqsoff
tracer.”h]”hŒ¸But neither will trace the time that interrupts and/or
preemption is disabled. This total time is the time that we can
not schedule. To record this time, use the preemptirqsoff
tracer.”…””}”(hjÝ&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MIhj†&  h²hubhÌ)”}”(hŒKAgain, using this trace is much like the irqsoff and preemptoff
tracers.
::”h]”hŒHAgain, using this trace is much like the irqsoff and preemptoff
tracers.”…””}”(hjë&  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MNhj†&  h²hubj´  )”}”(hX  # echo 0 > options/function-trace
# echo preemptirqsoff > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# ls -ltr
[...]
# echo 0 > tracing_on
# cat trace
# tracer: preemptirqsoff
#
# preemptirqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 100 us, #4/4, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: ls-2230 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: ata_scsi_queuecmd
#  => ended at:   ata_scsi_queuecmd
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
      ls-2230    3d...    0us+: _raw_spin_lock_irqsave <-ata_scsi_queuecmd
      ls-2230    3...1  100us : _raw_spin_unlock_irqrestore <-ata_scsi_queuecmd
      ls-2230    3...1  101us+: trace_preempt_on <-ata_scsi_queuecmd
      ls-2230    3...1  111us : <stack trace>
 => sub_preempt_count
 => _raw_spin_unlock_irqrestore
 => ata_scsi_queuecmd
 => scsi_dispatch_cmd
 => scsi_request_fn
 => __blk_run_queue_uncond
 => __blk_run_queue
 => blk_queue_bio
 => submit_bio_noacct
 => submit_bio
 => bh_submit
 => ext3_bread
 => ext3_dir_bread
 => htree_dirblock_to_tree
 => ext3_htree_fill_tree
 => ext3_readdir
 => vfs_readdir
 => sys_getdents
 => system_call_fastpath”h]”hX  # echo 0 > options/function-trace
# echo preemptirqsoff > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# ls -ltr
[...]
# echo 0 > tracing_on
# cat trace
# tracer: preemptirqsoff
#
# preemptirqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 100 us, #4/4, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: ls-2230 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: ata_scsi_queuecmd
#  => ended at:   ata_scsi_queuecmd
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
      ls-2230    3d...    0us+: _raw_spin_lock_irqsave <-ata_scsi_queuecmd
      ls-2230    3...1  100us : _raw_spin_unlock_irqrestore <-ata_scsi_queuecmd
      ls-2230    3...1  101us+: trace_preempt_on <-ata_scsi_queuecmd
      ls-2230    3...1  111us : <stack trace>
 => sub_preempt_count
 => _raw_spin_unlock_irqrestore
 => ata_scsi_queuecmd
 => scsi_dispatch_cmd
 => scsi_request_fn
 => __blk_run_queue_uncond
 => __blk_run_queue
 => blk_queue_bio
 => submit_bio_noacct
 => submit_bio
 => bh_submit
 => ext3_bread
 => ext3_dir_bread
 => htree_dirblock_to_tree
 => ext3_htree_fill_tree
 => ext3_readdir
 => vfs_readdir
 => sys_getdents
 => system_call_fastpath”…””}”hjù&  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MRhj†&  h²hubhÌ)”}”(hX  The trace_hardirqs_off_thunk is called from assembly on x86 when
interrupts are disabled in the assembly code. Without the
function tracing, we do not know if interrupts were enabled
within the preemption points. We do see that it started with
preemption enabled.”h]”hX  The trace_hardirqs_off_thunk is called from assembly on x86 when
interrupts are disabled in the assembly code. Without the
function tracing, we do not know if interrupts were enabled
within the preemption points. We do see that it started with
preemption enabled.”…””}”(hj'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‡hj†&  h²hubhÌ)”}”(hŒ)Here is a trace with function-trace set::”h]”hŒ(Here is a trace with function-trace set:”…””}”(hj'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj†&  h²hubj´  )”}”(hX  # tracer: preemptirqsoff
#
# preemptirqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 161 us, #339/339, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: ls-2269 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: schedule
#  => ended at:   mutex_unlock
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
kworker/-59      3...1    0us : __schedule <-schedule
kworker/-59      3d..1    0us : rcu_preempt_qs <-rcu_note_context_switch
kworker/-59      3d..1    1us : add_preempt_count <-_raw_spin_lock_irq
kworker/-59      3d..2    1us : deactivate_task <-__schedule
kworker/-59      3d..2    1us : dequeue_task <-deactivate_task
kworker/-59      3d..2    2us : update_rq_clock <-dequeue_task
kworker/-59      3d..2    2us : dequeue_task_fair <-dequeue_task
kworker/-59      3d..2    2us : update_curr <-dequeue_task_fair
kworker/-59      3d..2    2us : update_min_vruntime <-update_curr
kworker/-59      3d..2    3us : cpuacct_charge <-update_curr
kworker/-59      3d..2    3us : __rcu_read_lock <-cpuacct_charge
kworker/-59      3d..2    3us : __rcu_read_unlock <-cpuacct_charge
kworker/-59      3d..2    3us : update_cfs_rq_blocked_load <-dequeue_task_fair
kworker/-59      3d..2    4us : clear_buddies <-dequeue_task_fair
kworker/-59      3d..2    4us : account_entity_dequeue <-dequeue_task_fair
kworker/-59      3d..2    4us : update_min_vruntime <-dequeue_task_fair
kworker/-59      3d..2    4us : update_cfs_shares <-dequeue_task_fair
kworker/-59      3d..2    5us : hrtick_update <-dequeue_task_fair
kworker/-59      3d..2    5us : wq_worker_sleeping <-__schedule
kworker/-59      3d..2    5us : kthread_data <-wq_worker_sleeping
kworker/-59      3d..2    5us : put_prev_task_fair <-__schedule
kworker/-59      3d..2    6us : pick_next_task_fair <-pick_next_task
kworker/-59      3d..2    6us : clear_buddies <-pick_next_task_fair
kworker/-59      3d..2    6us : set_next_entity <-pick_next_task_fair
kworker/-59      3d..2    6us : update_stats_wait_end <-set_next_entity
      ls-2269    3d..2    7us : finish_task_switch <-__schedule
      ls-2269    3d..2    7us : _raw_spin_unlock_irq <-finish_task_switch
      ls-2269    3d..2    8us : do_IRQ <-ret_from_intr
      ls-2269    3d..2    8us : irq_enter <-do_IRQ
      ls-2269    3d..2    8us : rcu_irq_enter <-irq_enter
      ls-2269    3d..2    9us : add_preempt_count <-irq_enter
      ls-2269    3d.h2    9us : exit_idle <-do_IRQ
[...]
      ls-2269    3d.h3   20us : sub_preempt_count <-_raw_spin_unlock
      ls-2269    3d.h2   20us : irq_exit <-do_IRQ
      ls-2269    3d.h2   21us : sub_preempt_count <-irq_exit
      ls-2269    3d..3   21us : do_softirq <-irq_exit
      ls-2269    3d..3   21us : __do_softirq <-call_softirq
      ls-2269    3d..3   21us+: __local_bh_disable <-__do_softirq
      ls-2269    3d.s4   29us : sub_preempt_count <-_local_bh_enable_ip
      ls-2269    3d.s5   29us : sub_preempt_count <-_local_bh_enable_ip
      ls-2269    3d.s5   31us : do_IRQ <-ret_from_intr
      ls-2269    3d.s5   31us : irq_enter <-do_IRQ
      ls-2269    3d.s5   31us : rcu_irq_enter <-irq_enter
[...]
      ls-2269    3d.s5   31us : rcu_irq_enter <-irq_enter
      ls-2269    3d.s5   32us : add_preempt_count <-irq_enter
      ls-2269    3d.H5   32us : exit_idle <-do_IRQ
      ls-2269    3d.H5   32us : handle_irq <-do_IRQ
      ls-2269    3d.H5   32us : irq_to_desc <-handle_irq
      ls-2269    3d.H5   33us : handle_fasteoi_irq <-handle_irq
[...]
      ls-2269    3d.s5  158us : _raw_spin_unlock_irqrestore <-rtl8139_poll
      ls-2269    3d.s3  158us : net_rps_action_and_irq_enable.isra.65 <-net_rx_action
      ls-2269    3d.s3  159us : __local_bh_enable <-__do_softirq
      ls-2269    3d.s3  159us : sub_preempt_count <-__local_bh_enable
      ls-2269    3d..3  159us : idle_cpu <-irq_exit
      ls-2269    3d..3  159us : rcu_irq_exit <-irq_exit
      ls-2269    3d..3  160us : sub_preempt_count <-irq_exit
      ls-2269    3d...  161us : __mutex_unlock_slowpath <-mutex_unlock
      ls-2269    3d...  162us+: trace_hardirqs_on <-mutex_unlock
      ls-2269    3d...  186us : <stack trace>
 => __mutex_unlock_slowpath
 => mutex_unlock
 => process_output
 => n_tty_write
 => tty_write
 => vfs_write
 => sys_write
 => system_call_fastpath”h]”hX  # tracer: preemptirqsoff
#
# preemptirqsoff latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 161 us, #339/339, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: ls-2269 (uid:0 nice:0 policy:0 rt_prio:0)
#    -----------------
#  => started at: schedule
#  => ended at:   mutex_unlock
#
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
kworker/-59      3...1    0us : __schedule <-schedule
kworker/-59      3d..1    0us : rcu_preempt_qs <-rcu_note_context_switch
kworker/-59      3d..1    1us : add_preempt_count <-_raw_spin_lock_irq
kworker/-59      3d..2    1us : deactivate_task <-__schedule
kworker/-59      3d..2    1us : dequeue_task <-deactivate_task
kworker/-59      3d..2    2us : update_rq_clock <-dequeue_task
kworker/-59      3d..2    2us : dequeue_task_fair <-dequeue_task
kworker/-59      3d..2    2us : update_curr <-dequeue_task_fair
kworker/-59      3d..2    2us : update_min_vruntime <-update_curr
kworker/-59      3d..2    3us : cpuacct_charge <-update_curr
kworker/-59      3d..2    3us : __rcu_read_lock <-cpuacct_charge
kworker/-59      3d..2    3us : __rcu_read_unlock <-cpuacct_charge
kworker/-59      3d..2    3us : update_cfs_rq_blocked_load <-dequeue_task_fair
kworker/-59      3d..2    4us : clear_buddies <-dequeue_task_fair
kworker/-59      3d..2    4us : account_entity_dequeue <-dequeue_task_fair
kworker/-59      3d..2    4us : update_min_vruntime <-dequeue_task_fair
kworker/-59      3d..2    4us : update_cfs_shares <-dequeue_task_fair
kworker/-59      3d..2    5us : hrtick_update <-dequeue_task_fair
kworker/-59      3d..2    5us : wq_worker_sleeping <-__schedule
kworker/-59      3d..2    5us : kthread_data <-wq_worker_sleeping
kworker/-59      3d..2    5us : put_prev_task_fair <-__schedule
kworker/-59      3d..2    6us : pick_next_task_fair <-pick_next_task
kworker/-59      3d..2    6us : clear_buddies <-pick_next_task_fair
kworker/-59      3d..2    6us : set_next_entity <-pick_next_task_fair
kworker/-59      3d..2    6us : update_stats_wait_end <-set_next_entity
      ls-2269    3d..2    7us : finish_task_switch <-__schedule
      ls-2269    3d..2    7us : _raw_spin_unlock_irq <-finish_task_switch
      ls-2269    3d..2    8us : do_IRQ <-ret_from_intr
      ls-2269    3d..2    8us : irq_enter <-do_IRQ
      ls-2269    3d..2    8us : rcu_irq_enter <-irq_enter
      ls-2269    3d..2    9us : add_preempt_count <-irq_enter
      ls-2269    3d.h2    9us : exit_idle <-do_IRQ
[...]
      ls-2269    3d.h3   20us : sub_preempt_count <-_raw_spin_unlock
      ls-2269    3d.h2   20us : irq_exit <-do_IRQ
      ls-2269    3d.h2   21us : sub_preempt_count <-irq_exit
      ls-2269    3d..3   21us : do_softirq <-irq_exit
      ls-2269    3d..3   21us : __do_softirq <-call_softirq
      ls-2269    3d..3   21us+: __local_bh_disable <-__do_softirq
      ls-2269    3d.s4   29us : sub_preempt_count <-_local_bh_enable_ip
      ls-2269    3d.s5   29us : sub_preempt_count <-_local_bh_enable_ip
      ls-2269    3d.s5   31us : do_IRQ <-ret_from_intr
      ls-2269    3d.s5   31us : irq_enter <-do_IRQ
      ls-2269    3d.s5   31us : rcu_irq_enter <-irq_enter
[...]
      ls-2269    3d.s5   31us : rcu_irq_enter <-irq_enter
      ls-2269    3d.s5   32us : add_preempt_count <-irq_enter
      ls-2269    3d.H5   32us : exit_idle <-do_IRQ
      ls-2269    3d.H5   32us : handle_irq <-do_IRQ
      ls-2269    3d.H5   32us : irq_to_desc <-handle_irq
      ls-2269    3d.H5   33us : handle_fasteoi_irq <-handle_irq
[...]
      ls-2269    3d.s5  158us : _raw_spin_unlock_irqrestore <-rtl8139_poll
      ls-2269    3d.s3  158us : net_rps_action_and_irq_enable.isra.65 <-net_rx_action
      ls-2269    3d.s3  159us : __local_bh_enable <-__do_softirq
      ls-2269    3d.s3  159us : sub_preempt_count <-__local_bh_enable
      ls-2269    3d..3  159us : idle_cpu <-irq_exit
      ls-2269    3d..3  159us : rcu_irq_exit <-irq_exit
      ls-2269    3d..3  160us : sub_preempt_count <-irq_exit
      ls-2269    3d...  161us : __mutex_unlock_slowpath <-mutex_unlock
      ls-2269    3d...  162us+: trace_hardirqs_on <-mutex_unlock
      ls-2269    3d...  186us : <stack trace>
 => __mutex_unlock_slowpath
 => mutex_unlock
 => process_output
 => n_tty_write
 => tty_write
 => vfs_write
 => sys_write
 => system_call_fastpath”…””•       }”hj#'  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhj†&  h²hubhÌ)”}”(hX  This is an interesting trace. It started with kworker running and
scheduling out and ls taking over. But as soon as ls released the
rq lock and enabled interrupts (but not preemption) an interrupt
triggered. When the interrupt finished, it started running softirqs.
But while the softirq was running, another interrupt triggered.
When an interrupt is running inside a softirq, the annotation is 'H'.”h]”hX“  This is an interesting trace. It started with kworker running and
scheduling out and ls taking over. But as soon as ls released the
rq lock and enabled interrupts (but not preemption) an interrupt
triggered. When the interrupt finished, it started running softirqs.
But while the softirq was running, another interrupt triggered.
When an interrupt is running inside a softirq, the annotation is â€˜Hâ€™.”…””}”(hj1'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mêhj†&  h²hubeh}”(h]”Œpreemptirqsoff”ah ]”h"]”Œpreemptirqsoff”ah$]”h&]”uh1hµhh·h²hh³hÊh´M0ubh¶)”}”(hhh]”(h»)”}”(hŒwakeup”h]”hŒwakeup”…””}”(hjJ'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjG'  h²hh³hÊh´MóubhÌ)”}”(hŒÛOne common case that people are interested in tracing is the
time it takes for a task that is woken to actually wake up.
Now for non Real-Time tasks, this can be arbitrary. But tracing
it nonetheless can be interesting.”h]”hŒÛOne common case that people are interested in tracing is the
time it takes for a task that is woken to actually wake up.
Now for non Real-Time tasks, this can be arbitrary. But tracing
it nonetheless can be interesting.”…””}”(hjX'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MõhjG'  h²hubhÌ)”}”(hŒWithout function tracing::”h]”hŒWithout function tracing:”…””}”(hjf'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MúhjG'  h²hubj´  )”}”(hXG  # echo 0 > options/function-trace
# echo wakeup > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# chrt -f 5 sleep 1
# echo 0 > tracing_on
# cat trace
# tracer: wakeup
#
# wakeup latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 15 us, #4/4, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: kworker/3:1H-312 (uid:0 nice:-20 policy:0 rt_prio:0)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       3dNs7    0us :      0:120:R   + [003]   312:100:R kworker/3:1H
  <idle>-0       3dNs7    1us+: ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       3d..3   15us : __schedule <-schedule
  <idle>-0       3d..3   15us :      0:120:R ==> [003]   312:100:R kworker/3:1H”h]”hXG  # echo 0 > options/function-trace
# echo wakeup > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# chrt -f 5 sleep 1
# echo 0 > tracing_on
# cat trace
# tracer: wakeup
#
# wakeup latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 15 us, #4/4, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: kworker/3:1H-312 (uid:0 nice:-20 policy:0 rt_prio:0)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       3dNs7    0us :      0:120:R   + [003]   312:100:R kworker/3:1H
  <idle>-0       3dNs7    1us+: ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       3d..3   15us : __schedule <-schedule
  <idle>-0       3d..3   15us :      0:120:R ==> [003]   312:100:R kworker/3:1H”…””}”hjt'  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MühjG'  h²hubhÌ)”}”(hŒûThe tracer only traces the highest priority task in the system
to avoid tracing the normal circumstances. Here we see that
the kworker with a nice priority of -20 (not very nice), took
just 15 microseconds from the time it woke up, to the time it
ran.”h]”hŒûThe tracer only traces the highest priority task in the system
to avoid tracing the normal circumstances. Here we see that
the kworker with a nice priority of -20 (not very nice), took
just 15 microseconds from the time it woke up, to the time it
ran.”…””}”(hj‚'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjG'  h²hubhÌ)”}”(hŒqNon Real-Time tasks are not that interesting. A more interesting
trace is to concentrate only on Real-Time tasks.”h]”hŒqNon Real-Time tasks are not that interesting. A more interesting
trace is to concentrate only on Real-Time tasks.”…””}”(hj'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjG'  h²hubeh}”(h]”Œwakeup”ah ]”h"]”Œwakeup”ah$]”h&]”uh1hµhh·h²hh³hÊh´Móubh¶)”}”(hhh]”(h»)”}”(hŒ	wakeup_rt”h]”hŒ	wakeup_rt”…””}”(hj©'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj¦'  h²hh³hÊh´M#ubhÌ)”}”(hX»  In a Real-Time environment it is very important to know the
wakeup time it takes for the highest priority task that is woken
up to the time that it executes. This is also known as "schedule
latency". I stress the point that this is about RT tasks. It is
also important to know the scheduling latency of non-RT tasks,
but the average schedule latency is better for non-RT tasks.
Tools like LatencyTop are more appropriate for such
measurements.”h]”hX¿  In a Real-Time environment it is very important to know the
wakeup time it takes for the highest priority task that is woken
up to the time that it executes. This is also known as â€œschedule
latencyâ€. I stress the point that this is about RT tasks. It is
also important to know the scheduling latency of non-RT tasks,
but the average schedule latency is better for non-RT tasks.
Tools like LatencyTop are more appropriate for such
measurements.”…””}”(hj·'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M%hj¦'  h²hubhÌ)”}”(hX`  Real-Time environments are interested in the worst case latency.
That is the longest latency it takes for something to happen,
and not the average. We can have a very fast scheduler that may
only have a large latency once in a while, but that would not
work well with Real-Time tasks.  The wakeup_rt tracer was designed
to record the worst case wakeups of RT tasks. Non-RT tasks are
not recorded because the tracer only records one worst case and
tracing non-RT tasks that are unpredictable will overwrite the
worst case latency of RT tasks (just run the normal wakeup
tracer for a while to see that effect).”h]”hX`  Real-Time environments are interested in the worst case latency.
That is the longest latency it takes for something to happen,
and not the average. We can have a very fast scheduler that may
only have a large latency once in a while, but that would not
work well with Real-Time tasks.  The wakeup_rt tracer was designed
to record the worst case wakeups of RT tasks. Non-RT tasks are
not recorded because the tracer only records one worst case and
tracing non-RT tasks that are unpredictable will overwrite the
worst case latency of RT tasks (just run the normal wakeup
tracer for a while to see that effect).”…””}”(hjÅ'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M.hj¦'  h²hubhÌ)”}”(hŒåSince this tracer only deals with RT tasks, we will run this
slightly differently than we did with the previous tracers.
Instead of performing an 'ls', we will run 'sleep 1' under
'chrt' which changes the priority of the task.
::”h]”hŒîSince this tracer only deals with RT tasks, we will run this
slightly differently than we did with the previous tracers.
Instead of performing an â€˜lsâ€™, we will run â€˜sleep 1â€™ under
â€˜chrtâ€™ which changes the priority of the task.”…””}”(hjÓ'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M9hj¦'  h²hubj´  )”}”(hXL  # echo 0 > options/function-trace
# echo wakeup_rt > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# chrt -f 5 sleep 1
# echo 0 > tracing_on
# cat trace
# tracer: wakeup
#
# tracer: wakeup_rt
#
# wakeup_rt latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 5 us, #4/4, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sleep-2389 (uid:0 nice:0 policy:1 rt_prio:5)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       3d.h4    0us :      0:120:R   + [003]  2389: 94:R sleep
  <idle>-0       3d.h4    1us+: ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       3d..3    5us : __schedule <-schedule
  <idle>-0       3d..3    5us :      0:120:R ==> [003]  2389: 94:R sleep”h]”hXL  # echo 0 > options/function-trace
# echo wakeup_rt > current_tracer
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# chrt -f 5 sleep 1
# echo 0 > tracing_on
# cat trace
# tracer: wakeup
#
# tracer: wakeup_rt
#
# wakeup_rt latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 5 us, #4/4, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sleep-2389 (uid:0 nice:0 policy:1 rt_prio:5)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       3d.h4    0us :      0:120:R   + [003]  2389: 94:R sleep
  <idle>-0       3d.h4    1us+: ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       3d..3    5us : __schedule <-schedule
  <idle>-0       3d..3    5us :      0:120:R ==> [003]  2389: 94:R sleep”…””}”hjá'  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M?hj¦'  h²hubhÌ)”}”(hX7  Running this on an idle system, we see that it only took 5 microseconds
to perform the task switch.  Note, since the trace point in the schedule
is before the actual "switch", we stop the tracing when the recorded task
is about to schedule in. This may change if we add a new marker at the
end of the scheduler.”h]”hX;  Running this on an idle system, we see that it only took 5 microseconds
to perform the task switch.  Note, since the trace point in the schedule
is before the actual â€œswitchâ€, we stop the tracing when the recorded task
is about to schedule in. This may change if we add a new marker at the
end of the scheduler.”…””}”(hjï'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M_hj¦'  h²hubhÌ)”}”(hŒ×Notice that the recorded task is 'sleep' with the PID of 2389
and it has an rt_prio of 5. This priority is user-space priority
and not the internal kernel priority. The policy is 1 for
SCHED_FIFO and 2 for SCHED_RR.”h]”hŒÛNotice that the recorded task is â€˜sleepâ€™ with the PID of 2389
and it has an rt_prio of 5. This priority is user-space priority
and not the internal kernel priority. The policy is 1 for
SCHED_FIFO and 2 for SCHED_RR.”…””}”(hjý'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mehj¦'  h²hubhÌ)”}”(hŒGNote, that the trace data shows the internal priority (99 - rtprio).
::”h]”hŒDNote, that the trace data shows the internal priority (99 - rtprio).”…””}”(hj(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mjhj¦'  h²hubj´  )”}”(hŒF<idle>-0       3d..3    5us :      0:120:R ==> [003]  2389: 94:R sleep”h]”hŒF<idle>-0       3d..3    5us :      0:120:R ==> [003]  2389: 94:R sleep”…””}”hj(  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mmhj¦'  h²hubhÌ)”}”(hŒóThe 0:120:R means idle was running with a nice priority of 0 (120 - 120)
and in the running state 'R'. The sleep task was scheduled in with
2389: 94:R. That is the priority is the kernel rtprio (99 - 5 = 94)
and it too is in the running state.”h]”hŒ÷The 0:120:R means idle was running with a nice priority of 0 (120 - 120)
and in the running state â€˜Râ€™. The sleep task was scheduled in with
2389: 94:R. That is the priority is the kernel rtprio (99 - 5 = 94)
and it too is in the running state.”…””}”(hj'(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mohj¦'  h²hubhÌ)”}”(hŒ8Doing the same with chrt -r 5 and function-trace set.
::”h]”hŒ5Doing the same with chrt -r 5 and function-trace set.”…””}”(hj5(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mthj¦'  h²hubj´  )”}”(hXP  echo 1 > options/function-trace

# tracer: wakeup_rt
#
# wakeup_rt latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 29 us, #85/85, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sleep-2448 (uid:0 nice:0 policy:1 rt_prio:5)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       3d.h4    1us+:      0:120:R   + [003]  2448: 94:R sleep
  <idle>-0       3d.h4    2us : ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       3d.h3    3us : check_preempt_curr <-ttwu_do_wakeup
  <idle>-0       3d.h3    3us : resched_curr <-check_preempt_curr
  <idle>-0       3dNh3    4us : task_woken_rt <-ttwu_do_wakeup
  <idle>-0       3dNh3    4us : _raw_spin_unlock <-try_to_wake_up
  <idle>-0       3dNh3    4us : sub_preempt_count <-_raw_spin_unlock
  <idle>-0       3dNh2    5us : ttwu_stat <-try_to_wake_up
  <idle>-0       3dNh2    5us : _raw_spin_unlock_irqrestore <-try_to_wake_up
  <idle>-0       3dNh2    6us : sub_preempt_count <-_raw_spin_unlock_irqrestore
  <idle>-0       3dNh1    6us : _raw_spin_lock <-__run_hrtimer
  <idle>-0       3dNh1    6us : add_preempt_count <-_raw_spin_lock
  <idle>-0       3dNh2    7us : _raw_spin_unlock <-hrtimer_interrupt
  <idle>-0       3dNh2    7us : sub_preempt_count <-_raw_spin_unlock
  <idle>-0       3dNh1    7us : tick_program_event <-hrtimer_interrupt
  <idle>-0       3dNh1    7us : clockevents_program_event <-tick_program_event
  <idle>-0       3dNh1    8us : ktime_get <-clockevents_program_event
  <idle>-0       3dNh1    8us : lapic_next_event <-clockevents_program_event
  <idle>-0       3dNh1    8us : irq_exit <-smp_apic_timer_interrupt
  <idle>-0       3dNh1    9us : sub_preempt_count <-irq_exit
  <idle>-0       3dN.2    9us : idle_cpu <-irq_exit
  <idle>-0       3dN.2    9us : rcu_irq_exit <-irq_exit
  <idle>-0       3dN.2   10us : rcu_eqs_enter_common.isra.45 <-rcu_irq_exit
  <idle>-0       3dN.2   10us : sub_preempt_count <-irq_exit
  <idle>-0       3.N.1   11us : rcu_idle_exit <-cpu_idle
  <idle>-0       3dN.1   11us : rcu_eqs_exit_common.isra.43 <-rcu_idle_exit
  <idle>-0       3.N.1   11us : tick_nohz_idle_exit <-cpu_idle
  <idle>-0       3dN.1   12us : menu_hrtimer_cancel <-tick_nohz_idle_exit
  <idle>-0       3dN.1   12us : ktime_get <-tick_nohz_idle_exit
  <idle>-0       3dN.1   12us : tick_do_update_jiffies64 <-tick_nohz_idle_exit
  <idle>-0       3dN.1   13us : cpu_load_update_nohz <-tick_nohz_idle_exit
  <idle>-0       3dN.1   13us : _raw_spin_lock <-cpu_load_update_nohz
  <idle>-0       3dN.1   13us : add_preempt_count <-_raw_spin_lock
  <idle>-0       3dN.2   13us : __cpu_load_update <-cpu_load_update_nohz
  <idle>-0       3dN.2   14us : sched_avg_update <-__cpu_load_update
  <idle>-0       3dN.2   14us : _raw_spin_unlock <-cpu_load_update_nohz
  <idle>-0       3dN.2   14us : sub_preempt_count <-_raw_spin_unlock
  <idle>-0       3dN.1   15us : calc_load_nohz_stop <-tick_nohz_idle_exit
  <idle>-0       3dN.1   15us : touch_softlockup_watchdog <-tick_nohz_idle_exit
  <idle>-0       3dN.1   15us : hrtimer_cancel <-tick_nohz_idle_exit
  <idle>-0       3dN.1   15us : hrtimer_try_to_cancel <-hrtimer_cancel
  <idle>-0       3dN.1   16us : lock_hrtimer_base.isra.18 <-hrtimer_try_to_cancel
  <idle>-0       3dN.1   16us : _raw_spin_lock_irqsave <-lock_hrtimer_base.isra.18
  <idle>-0       3dN.1   16us : add_preempt_count <-_raw_spin_lock_irqsave
  <idle>-0       3dN.2   17us : __remove_hrtimer <-remove_hrtimer.part.16
  <idle>-0       3dN.2   17us : hrtimer_force_reprogram <-__remove_hrtimer
  <idle>-0       3dN.2   17us : tick_program_event <-hrtimer_force_reprogram
  <idle>-0       3dN.2   18us : clockevents_program_event <-tick_program_event
  <idle>-0       3dN.2   18us : ktime_get <-clockevents_program_event
  <idle>-0       3dN.2   18us : lapic_next_event <-clockevents_program_event
  <idle>-0       3dN.2   19us : _raw_spin_unlock_irqrestore <-hrtimer_try_to_cancel
  <idle>-0       3dN.2   19us : sub_preempt_count <-_raw_spin_unlock_irqrestore
  <idle>-0       3dN.1   19us : hrtimer_forward <-tick_nohz_idle_exit
  <idle>-0       3dN.1   20us : ktime_add_safe <-hrtimer_forward
  <idle>-0       3dN.1   20us : ktime_add_safe <-hrtimer_forward
  <idle>-0       3dN.1   20us : hrtimer_start_range_ns <-hrtimer_start_expires.constprop.11
  <idle>-0       3dN.1   20us : __hrtimer_start_range_ns <-hrtimer_start_range_ns
  <idle>-0       3dN.1   21us : lock_hrtimer_base.isra.18 <-__hrtimer_start_range_ns
  <idle>-0       3dN.1   21us : _raw_spin_lock_irqsave <-lock_hrtimer_base.isra.18
  <idle>-0       3dN.1   21us : add_preempt_count <-_raw_spin_lock_irqsave
  <idle>-0       3dN.2   22us : ktime_add_safe <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   22us : enqueue_hrtimer <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   22us : tick_program_event <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   23us : clockevents_program_event <-tick_program_event
  <idle>-0       3dN.2   23us : ktime_get <-clockevents_program_event
  <idle>-0       3dN.2   23us : lapic_next_event <-clockevents_program_event
  <idle>-0       3dN.2   24us : _raw_spin_unlock_irqrestore <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   24us : sub_preempt_count <-_raw_spin_unlock_irqrestore
  <idle>-0       3dN.1   24us : account_idle_ticks <-tick_nohz_idle_exit
  <idle>-0       3dN.1   24us : account_idle_time <-account_idle_ticks
  <idle>-0       3.N.1   25us : sub_preempt_count <-cpu_idle
  <idle>-0       3.N..   25us : schedule <-cpu_idle
  <idle>-0       3.N..   25us : __schedule <-preempt_schedule
  <idle>-0       3.N..   26us : add_preempt_count <-__schedule
  <idle>-0       3.N.1   26us : rcu_note_context_switch <-__schedule
  <idle>-0       3.N.1   26us : rcu_sched_qs <-rcu_note_context_switch
  <idle>-0       3dN.1   27us : rcu_preempt_qs <-rcu_note_context_switch
  <idle>-0       3.N.1   27us : _raw_spin_lock_irq <-__schedule
  <idle>-0       3dN.1   27us : add_preempt_count <-_raw_spin_lock_irq
  <idle>-0       3dN.2   28us : put_prev_task_idle <-__schedule
  <idle>-0       3dN.2   28us : pick_next_task_stop <-pick_next_task
  <idle>-0       3dN.2   28us : pick_next_task_rt <-pick_next_task
  <idle>-0       3dN.2   29us : dequeue_pushable_task <-pick_next_task_rt
  <idle>-0       3d..3   29us : __schedule <-preempt_schedule
  <idle>-0       3d..3   30us :      0:120:R ==> [003]  2448: 94:R sleep”h]”hXP  echo 1 > options/function-trace

# tracer: wakeup_rt
#
# wakeup_rt latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 29 us, #85/85, CPU#3 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sleep-2448 (uid:0 nice:0 policy:1 rt_prio:5)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       3d.h4    1us+:      0:120:R   + [003]  2448: 94:R sleep
  <idle>-0       3d.h4    2us : ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       3d.h3    3us : check_preempt_curr <-ttwu_do_wakeup
  <idle>-0       3d.h3    3us : resched_curr <-check_preempt_curr
  <idle>-0       3dNh3    4us : task_woken_rt <-ttwu_do_wakeup
  <idle>-0       3dNh3    4us : _raw_spin_unlock <-try_to_wake_up
  <idle>-0       3dNh3    4us : sub_preempt_count <-_raw_spin_unlock
  <idle>-0       3dNh2    5us : ttwu_stat <-try_to_wake_up
  <idle>-0       3dNh2    5us : _raw_spin_unlock_irqrestore <-try_to_wake_up
  <idle>-0       3dNh2    6us : sub_preempt_count <-_raw_spin_unlock_irqrestore
  <idle>-0       3dNh1    6us : _raw_spin_lock <-__run_hrtimer
  <idle>-0       3dNh1    6us : add_preempt_count <-_raw_spin_lock
  <idle>-0       3dNh2    7us : _raw_spin_unlock <-hrtimer_interrupt
  <idle>-0       3dNh2    7us : sub_preempt_count <-_raw_spin_unlock
  <idle>-0       3dNh1    7us : tick_program_event <-hrtimer_interrupt
  <idle>-0       3dNh1    7us : clockevents_program_event <-tick_program_event
  <idle>-0       3dNh1    8us : ktime_get <-clockevents_program_event
  <idle>-0       3dNh1    8us : lapic_next_event <-clockevents_program_event
  <idle>-0       3dNh1    8us : irq_exit <-smp_apic_timer_interrupt
  <idle>-0       3dNh1    9us : sub_preempt_count <-irq_exit
  <idle>-0       3dN.2    9us : idle_cpu <-irq_exit
  <idle>-0       3dN.2    9us : rcu_irq_exit <-irq_exit
  <idle>-0       3dN.2   10us : rcu_eqs_enter_common.isra.45 <-rcu_irq_exit
  <idle>-0       3dN.2   10us : sub_preempt_count <-irq_exit
  <idle>-0       3.N.1   11us : rcu_idle_exit <-cpu_idle
  <idle>-0       3dN.1   11us : rcu_eqs_exit_common.isra.43 <-rcu_idle_exit
  <idle>-0       3.N.1   11us : tick_nohz_idle_exit <-cpu_idle
  <idle>-0       3dN.1   12us : menu_hrtimer_cancel <-tick_nohz_idle_exit
  <idle>-0       3dN.1   12us : ktime_get <-tick_nohz_idle_exit
  <idle>-0       3dN.1   12us : tick_do_update_jiffies64 <-tick_nohz_idle_exit
  <idle>-0       3dN.1   13us : cpu_load_update_nohz <-tick_nohz_idle_exit
  <idle>-0       3dN.1   13us : _raw_spin_lock <-cpu_load_update_nohz
  <idle>-0       3dN.1   13us : add_preempt_count <-_raw_spin_lock
  <idle>-0       3dN.2   13us : __cpu_load_update <-cpu_load_update_nohz
  <idle>-0       3dN.2   14us : sched_avg_update <-__cpu_load_update
  <idle>-0       3dN.2   14us : _raw_spin_unlock <-cpu_load_update_nohz
  <idle>-0       3dN.2   14us : sub_preempt_count <-_raw_spin_unlock
  <idle>-0       3dN.1   15us : calc_load_nohz_stop <-tick_nohz_idle_exit
  <idle>-0       3dN.1   15us : touch_softlockup_watchdog <-tick_nohz_idle_exit
  <idle>-0       3dN.1   15us : hrtimer_cancel <-tick_nohz_idle_exit
  <idle>-0       3dN.1   15us : hrtimer_try_to_cancel <-hrtimer_cancel
  <idle>-0       3dN.1   16us : lock_hrtimer_base.isra.18 <-hrtimer_try_to_cancel
  <idle>-0       3dN.1   16us : _raw_spin_lock_irqsave <-lock_hrtimer_base.isra.18
  <idle>-0       3dN.1   16us : add_preempt_count <-_raw_spin_lock_irqsave
  <idle>-0       3dN.2   17us : __remove_hrtimer <-remove_hrtimer.part.16
  <idle>-0       3dN.2   17us : hrtimer_force_reprogram <-__remove_hrtimer
  <idle>-0       3dN.2   17us : tick_program_event <-hrtimer_force_reprogram
  <idle>-0       3dN.2   18us : clockevents_program_event <-tick_program_event
  <idle>-0       3dN.2   18us : ktime_get <-clockevents_program_event
  <idle>-0       3dN.2   18us : lapic_next_event <-clockevents_program_event
  <idle>-0       3dN.2   19us : _raw_spin_unlock_irqrestore <-hrtimer_try_to_cancel
  <idle>-0       3dN.2   19us : sub_preempt_count <-_raw_spin_unlock_irqrestore
  <idle>-0       3dN.1   19us : hrtimer_forward <-tick_nohz_idle_exit
  <idle>-0       3dN.1   20us : ktime_add_safe <-hrtimer_forward
  <idle>-0       3dN.1   20us : ktime_add_safe <-hrtimer_forward
  <idle>-0       3dN.1   20us : hrtimer_start_range_ns <-hrtimer_start_expires.constprop.11
  <idle>-0       3dN.1   20us : __hrtimer_start_range_ns <-hrtimer_start_range_ns
  <idle>-0       3dN.1   21us : lock_hrtimer_base.isra.18 <-__hrtimer_start_range_ns
  <idle>-0       3dN.1   21us : _raw_spin_lock_irqsave <-lock_hrtimer_base.isra.18
  <idle>-0       3dN.1   21us : add_preempt_count <-_raw_spin_lock_irqsave
  <idle>-0       3dN.2   22us : ktime_add_safe <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   22us : enqueue_hrtimer <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   22us : tick_program_event <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   23us : clockevents_program_event <-tick_program_event
  <idle>-0       3dN.2   23us : ktime_get <-clockevents_program_event
  <idle>-0       3dN.2   23us : lapic_next_event <-clockevents_program_event
  <idle>-0       3dN.2   24us : _raw_spin_unlock_irqrestore <-__hrtimer_start_range_ns
  <idle>-0       3dN.2   24us : sub_preempt_count <-_raw_spin_unlock_irqrestore
  <idle>-0       3dN.1   24us : account_idle_ticks <-tick_nohz_idle_exit
  <idle>-0       3dN.1   24us : account_idle_time <-account_idle_ticks
  <idle>-0       3.N.1   25us : sub_preempt_count <-cpu_idle
  <idle>-0       3.N..   25us : schedule <-cpu_idle
  <idle>-0       3.N..   25us : __schedule <-preempt_schedule
  <idle>-0       3.N..   26us : add_preempt_count <-__schedule
  <idle>-0       3.N.1   26us : rcu_note_context_switch <-__schedule
  <idle>-0       3.N.1   26us : rcu_sched_qs <-rcu_note_context_switch
  <idle>-0       3dN.1   27us : rcu_preempt_qs <-rcu_note_context_switch
  <idle>-0       3.N.1   27us : _raw_spin_lock_irq <-__schedule
  <idle>-0       3dN.1   27us : add_preempt_count <-_raw_spin_lock_irq
  <idle>-0       3dN.2   28us : put_prev_task_idle <-__schedule
  <idle>-0       3dN.2   28us : pick_next_task_stop <-pick_next_task
  <idle>-0       3dN.2   28us : pick_next_task_rt <-pick_next_task
  <idle>-0       3dN.2   29us : dequeue_pushable_task <-pick_next_task_rt
  <idle>-0       3d..3   29us : __schedule <-preempt_schedule
  <idle>-0       3d..3   30us :      0:120:R ==> [003]  2448: 94:R sleep”…””}”hjC(  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mwhj¦'  h²hubhÌ)”}”(hŒcThis isn't that big of a trace, even with function tracing enabled,
so I included the entire trace.”h]”hŒeThis isnâ€™t that big of a trace, even with function tracing enabled,
so I included the entire trace.”…””}”(hjQ(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Màhj¦'  h²hubhÌ)”}”(hŒ½The interrupt went off while when the system was idle. Somewhere
before task_woken_rt() was called, the NEED_RESCHED flag was set,
this is indicated by the first occurrence of the 'N' flag.”h]”hŒÁThe interrupt went off while when the system was idle. Somewhere
before task_woken_rt() was called, the NEED_RESCHED flag was set,
this is indicated by the first occurrence of the â€˜Nâ€™ flag.”…””}”(hj_(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mãhj¦'  h²hubeh}”(h]”Œ	wakeup-rt”ah ]”h"]”Œ	wakeup_rt”ah$]”h&]”uh1hµhh·h²hh³hÊh´M#ubh¶)”}”(hhh]”(h»)”}”(hŒLatency tracing and events”h]”hŒLatency tracing and events”…””}”(hjx(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhju(  h²hh³hÊh´MèubhÌ)”}”(hŒÊAs function tracing can induce a much larger latency, but without
seeing what happens within the latency it is hard to know what
caused it. There is a middle ground, and that is with enabling
events.
::”h]”hŒÇAs function tracing can induce a much larger latency, but without
seeing what happens within the latency it is hard to know what
caused it. There is a middle ground, and that is with enabling
events.”…””}”(hj†(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Méhju(  h²hubj´  )”}”(hXä  # echo 0 > options/function-trace
# echo wakeup_rt > current_tracer
# echo 1 > events/enable
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# chrt -f 5 sleep 1
# echo 0 > tracing_on
# cat trace
# tracer: wakeup_rt
#
# wakeup_rt latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 6 us, #12/12, CPU#2 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sleep-5882 (uid:0 nice:0 policy:1 rt_prio:5)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       2d.h4    0us :      0:120:R   + [002]  5882: 94:R sleep
  <idle>-0       2d.h4    0us : ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       2d.h4    1us : sched_wakeup: comm=sleep pid=5882 prio=94 success=1 target_cpu=002
  <idle>-0       2dNh2    1us : hrtimer_expire_exit: hrtimer=ffff88007796feb8
  <idle>-0       2.N.2    2us : power_end: cpu_id=2
  <idle>-0       2.N.2    3us : cpu_idle: state=4294967295 cpu_id=2
  <idle>-0       2dN.3    4us : hrtimer_cancel: hrtimer=ffff88007d50d5e0
  <idle>-0       2dN.3    4us : hrtimer_start: hrtimer=ffff88007d50d5e0 function=tick_sched_timer expires=34311211000000 softexpires=34311211000000
  <idle>-0       2.N.2    5us : rcu_utilization: Start context switch
  <idle>-0       2.N.2    5us : rcu_utilization: End context switch
  <idle>-0       2d..3    6us : __schedule <-schedule
  <idle>-0       2d..3    6us :      0:120:R ==> [002]  5882: 94:R sleep”h]”hXä  # echo 0 > options/function-trace
# echo wakeup_rt > current_tracer
# echo 1 > events/enable
# echo 1 > tracing_on
# echo 0 > tracing_max_latency
# chrt -f 5 sleep 1
# echo 0 > tracing_on
# cat trace
# tracer: wakeup_rt
#
# wakeup_rt latency trace v1.1.5 on 3.8.0-test+
# --------------------------------------------------------------------
# latency: 6 us, #12/12, CPU#2 | (M:preempt VP:0, KP:0, SP:0 HP:0 #P:4)
#    -----------------
#    | task: sleep-5882 (uid:0 nice:0 policy:1 rt_prio:5)
#    -----------------
#
#                  _------=> CPU#
#                 / _-----=> irqs-off
#                | / _----=> need-resched
#                || / _---=> hardirq/softirq
#                ||| / _--=> preempt-depth
#                |||| /     delay
#  cmd     pid   ||||| time  |   caller
#     \   /      |||||  \    |   /
  <idle>-0       2d.h4    0us :      0:120:R   + [002]  5882: 94:R sleep
  <idle>-0       2d.h4    0us : ttwu_do_activate.constprop.87 <-try_to_wake_up
  <idle>-0       2d.h4    1us : sched_wakeup: comm=sleep pid=5882 prio=94 success=1 target_cpu=002
  <idle>-0       2dNh2    1us : hrtimer_expire_exit: hrtimer=ffff88007796feb8
  <idle>-0       2.N.2    2us : power_end: cpu_id=2
  <idle>-0       2.N.2    3us : cpu_idle: state=4294967295 cpu_id=2
  <idle>-0       2dN.3    4us : hrtimer_cancel: hrtimer=ffff88007d50d5e0
  <idle>-0       2dN.3    4us : hrtimer_start: hrtimer=ffff88007d50d5e0 function=tick_sched_timer expires=34311211000000 softexpires=34311211000000
  <idle>-0       2.N.2    5us : rcu_utilization: Start context switch
  <idle>-0       2.N.2    5us : rcu_utilization: End context switch
  <idle>-0       2d..3    6us : __schedule <-schedule
  <idle>-0       2d..3    6us :      0:120:R ==> [002]  5882: 94:R sleep”…””}”hj”(  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mïhju(  h²hubeh}”(h]”Œlatency-tracing-and-events”ah ]”h"]”Œlatency tracing and events”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mèubh¶)”}”(hhh]”(h»)”}”(hŒHardware Latency Detector”h]”hŒHardware Latency Detector”…””}”(hj­(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjª(  h²hh³hÊh´M	ubhÌ)”}”(hŒIThe hardware latency detector is executed by enabling the "hwlat" tracer.”h]”hŒMThe hardware latency detector is executed by enabling the â€œhwlatâ€ tracer.”…””}”(hj»(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M	hjª(  h²hubhÌ)”}”(hŒ‹NOTE, this tracer will affect the performance of the system as it will
periodically make a CPU constantly busy with interrupts disabled.
::”h]”hŒˆNOTE, this tracer will affect the performance of the system as it will
periodically make a CPU constantly busy with interrupts disabled.”…””}”(hjÉ(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M	hjª(  h²hubj´  )”}”(hX}  # echo hwlat > current_tracer
# sleep 100
# cat trace
# tracer: hwlat
#
# entries-in-buffer/entries-written: 13/13   #P:8
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
           <...>-1729  [001] d...   678.473449: #1     inner/outer(us):   11/12    ts:1581527483.343962693 count:6
           <...>-1729  [004] d...   689.556542: #2     inner/outer(us):   16/9     ts:1581527494.889008092 count:1
           <...>-1729  [005] d...   714.756290: #3     inner/outer(us):   16/16    ts:1581527519.678961629 count:5
           <...>-1729  [001] d...   718.788247: #4     inner/outer(us):    9/17    ts:1581527523.889012713 count:1
           <...>-1729  [002] d...   719.796341: #5     inner/outer(us):   13/9     ts:1581527524.912872606 count:1
           <...>-1729  [006] d...   844.787091: #6     inner/outer(us):    9/12    ts:1581527649.889048502 count:2
           <...>-1729  [003] d...   849.827033: #7     inner/outer(us):   18/9     ts:1581527654.889013793 count:1
           <...>-1729  [007] d...   853.859002: #8     inner/outer(us):    9/12    ts:1581527658.889065736 count:1
           <...>-1729  [001] d...   855.874978: #9     inner/outer(us):    9/11    ts:1581527660.861991877 count:1
           <...>-1729  [001] d...   863.938932: #10    inner/outer(us):    9/11    ts:1581527668.970010500 count:1 nmi-total:7 nmi-count:1
           <...>-1729  [007] d...   878.050780: #11    inner/outer(us):    9/12    ts:1581527683.385002600 count:1 nmi-total:5 nmi-count:1
           <...>-1729  [007] d...   886.114702: #12    inner/outer(us):    9/12    ts:1581527691.385001600 count:1”h]”hX}  # echo hwlat > current_tracer
# sleep 100
# cat trace
# tracer: hwlat
#
# entries-in-buffer/entries-written: 13/13   #P:8
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
           <...>-1729  [001] d...   678.473449: #1     inner/outer(us):   11/12    ts:1581527483.343962693 count:6
           <...>-1729  [004] d...   689.556542: #2     inner/outer(us):   16/9     ts:1581527494.889008092 count:1
           <...>-1729  [005] d...   714.756290: #3     inner/outer(us):   16/16    ts:1581527519.678961629 count:5
           <...>-1729  [001] d...   718.788247: #4     inner/outer(us):    9/17    ts:1581527523.889012713 count:1
           <...>-1729  [002] d...   719.796341: #5     inner/outer(us):   13/9     ts:1581527524.912872606 count:1
           <...>-1729  [006] d...   844.787091: #6     inner/outer(us):    9/12    ts:1581527649.889048502 count:2
           <...>-1729  [003] d...   849.827033: #7     inner/outer(us):   18/9     ts:1581527654.889013793 count:1
           <...>-1729  [007] d...   853.859002: #8     inner/outer(us):    9/12    ts:1581527658.889065736 count:1
           <...>-1729  [001] d...   855.874978: #9     inner/outer(us):    9/11    ts:1581527660.861991877 count:1
           <...>-1729  [001] d...   863.938932: #10    inner/outer(us):    9/11    ts:1581527668.970010500 count:1 nmi-total:7 nmi-count:1
           <...>-1729  [007] d...   878.050780: #11    inner/outer(us):    9/12    ts:1581527683.385002600 count:1 nmi-total:5 nmi-count:1
           <...>-1729  [007] d...   886.114702: #12    inner/outer(us):    9/12    ts:1581527691.385001600 count:1”…””}”hj×(  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M	hjª(  h²hubhÌ)”}”(hŒ…The above output is somewhat the same in the header. All events will have
interrupts disabled 'd'. Under the FUNCTION title there is:”h]”hŒ‰The above output is somewhat the same in the header. All events will have
interrupts disabled â€˜dâ€™. Under the FUNCTION title there is:”…””}”(hjå(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M;	hjª(  h²hubjh  )”}”(hX¡  #1
       This is the count of events recorded that were greater than the
       tracing_threshold (See below).

inner/outer(us):   11/11

     This shows two numbers as "inner latency" and "outer latency". The test
     runs in a loop checking a timestamp twice. The latency detected within
     the two timestamps is the "inner latency" and the latency detected
     after the previous timestamp and the next timestamp in the loop is
     the "outer latency".

ts:1581527483.343962693

     The absolute timestamp that the first latency was recorded in the window.

count:6

     The number of times a latency was detected during the window.

nmi-total:7 nmi-count:1

     On architectures that support it, if an NMI comes in during the
     test, the time spent in NMI is reported in "nmi-total" (in
     microseconds).

     All architectures that have NMIs will show the "nmi-count" if an
     NMI comes in during the test.
”h]”(jŽ  )”}”(hhh]”j“  )”}”(hŒb#1
This is the count of events recorded that were greater than the
tracing_threshold (See below).
”h]”(j™  )”}”(hŒ#1”h]”hŒ#1”…””}”(hjþ(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´M@	hjú(  ubj©  )”}”(hhh]”hÌ)”}”(hŒ^This is the count of events recorded that were greater than the
tracing_threshold (See below).”h]”hŒ^This is the count of events recorded that were greater than the
tracing_threshold (See below).”…””}”(hj)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M?	hj)  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjú(  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´M@	hj÷(  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjó(  ubhÌ)”}”(hŒinner/outer(us):   11/11”h]”hŒinner/outer(us):   11/11”…””}”(hj/)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MB	hjó(  ubjh  )”}”(hX*  This shows two numbers as "inner latency" and "outer latency". The test
runs in a loop checking a timestamp twice. The latency detected within
the two timestamps is the "inner latency" and the latency detected
after the previous timestamp and the next timestamp in the loop is
the "outer latency".
”h]”hÌ)”}”(hX)  This shows two numbers as "inner latency" and "outer latency". The test
runs in a loop checking a timestamp twice. The latency detected within
the two timestamps is the "inner latency" and the latency detected
after the previous timestamp and the next timestamp in the loop is
the "outer latency".”h]”hX9  This shows two numbers as â€œinner latencyâ€ and â€œouter latencyâ€. The test
runs in a loop checking a timestamp twice. The latency detected within
the two timestamps is the â€œinner latencyâ€ and the latency detected
after the previous timestamp and the next timestamp in the loop is
the â€œouter latencyâ€.”…””}”(hjA)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MD	hj=)  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MD	hjó(  ubhÌ)”}”(hŒts:1581527483.343962693”h]”hŒts:1581527483.343962693”…””}”(hjU)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MJ	hjó(  ubjh  )”}”(hŒJThe absolute timestamp that the first latency was recorded in the window.
”h]”hÌ)”}”(hŒIThe absolute timestamp that the first latency was recorded in the window.”h]”hŒIThe absolute timestamp that the first latency was recorded in the window.”…””}”(hjg)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´ML	hjc)  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´ML	hjó(  ubhÌ)”}”(hŒcount:6”h]”hŒcount:6”…””}”(hj{)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MN	hjó(  ubjh  )”}”(hŒ>The number of times a latency was detected during the window.
”h]”hÌ)”}”(hŒ=The number of times a latency was detected during the window.”h]”hŒ=The number of times a latency was detected during the window.”…””}”(hj)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MP	hj‰)  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MP	hjó(  ubhÌ)”}”(hŒnmi-total:7 nmi-count:1”h]”hŒnmi-total:7 nmi-count:1”…””}”(hj¡)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MR	hjó(  ubjh  )”}”(hŒêOn architectures that support it, if an NMI comes in during the
test, the time spent in NMI is reported in "nmi-total" (in
microseconds).

All architectures that have NMIs will show the "nmi-count" if an
NMI comes in during the test.
”h]”(hÌ)”}”(hŒ‰On architectures that support it, if an NMI comes in during the
test, the time spent in NMI is reported in "nmi-total" (in
microseconds).”h]”hŒOn architectures that support it, if an NMI comes in during the
test, the time spent in NMI is reported in â€œnmi-totalâ€ (in
microseconds).”…””}”(hj³)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MT	hj¯)  ubhÌ)”}”(hŒ^All architectures that have NMIs will show the "nmi-count" if an
NMI comes in during the test.”h]”hŒbAll architectures that have NMIs will show the â€œnmi-countâ€ if an
NMI comes in during the test.”…””}”(hjÁ)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MX	hj¯)  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MT	hjó(  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M>	hjª(  h²hubhÌ)”}”(hŒhwlat files:”h]”hŒhwlat files:”…””}”(hjÛ)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M[	hjª(  h²hubjh  )”}”(hXÍ  tracing_threshold
      This gets automatically set to "10" to represent 10
      microseconds. This is the threshold of latency that
      needs to be detected before the trace will be recorded.

      Note, when hwlat tracer is finished (another tracer is
      written into "current_tracer"), the original value for
      tracing_threshold is placed back into this file.

hwlat_detector/width
      The length of time the test runs with interrupts disabled.

hwlat_detector/window
      The length of time of the window which the test
      runs. That is, the test will run for "width"
      microseconds per "window" microseconds

tracing_cpumask
      When the test is started. A kernel thread is created that
      runs the test. This thread will alternate between CPUs
      listed in the tracing_cpumask between each period
      (one "window"). To limit the test to specific CPUs
      set the mask in this file to only the CPUs that the test
      should run on.
”h]”jŽ  )”}”(hhh]”(j“  )”}”(hXR  tracing_threshold
This gets automatically set to "10" to represent 10
microseconds. This is the threshold of latency that
needs to be detected before the trace will be recorded.

Note, when hwlat tracer is finished (another tracer is
written into "current_tracer"), the original value for
tracing_threshold is placed back into this file.
”h]”(j™  )”}”(hŒtracing_threshold”h]”hŒtracing_threshold”…””}”(hjô)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Md	hjð)  ubj©  )”}”(hhh]”(hÌ)”}”(hŒŸThis gets automatically set to "10" to represent 10
microseconds. This is the threshold of latency that
needs to be detected before the trace will be recorded.”h]”hŒ£This gets automatically set to â€œ10â€ to represent 10
microseconds. This is the threshold of latency that
needs to be detected before the trace will be recorded.”…””}”(hj*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M^	hj*  ubhÌ)”}”(hŒžNote, when hwlat tracer is finished (another tracer is
written into "current_tracer"), the original value for
tracing_threshold is placed back into this file.”h]”hŒ¢Note, when hwlat tracer is finished (another tracer is
written into â€œcurrent_tracerâ€), the original value for
tracing_threshold is placed back into this file.”…””}”(hj*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mb	hj*  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjð)  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Md	hjí)  ubj“  )”}”(hŒPhwlat_detector/width
The length of time the test runs with interrupts disabled.
”h]”(j™  )”}”(hŒhwlat_detector/width”h]”hŒhwlat_detector/width”…””}”(hj1*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mg	hj-*  ubj©  )”}”(hhh]”hÌ)”}”(hŒ:The length of time the test runs with interrupts disabled.”h]”hŒ:The length of time the test runs with interrupts disabled.”…””}”(hjB*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mg	hj?*  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj-*  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mg	hjí)  ubj“  )”}”(hŒšhwlat_detector/window
The length of time of the window which the test
runs. That is, the test will run for "width"
microseconds per "window" microseconds
”h]”(j™  )”}”(hŒhwlat_detector/window”h]”hŒhwlat_detector/window”…””}”(hj`*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Ml	hj\*  ubj©  )”}”(hhh]”hÌ)”}”(hŒƒThe length of time of the window which the test
runs. That is, the test will run for "width"
microseconds per "window" microseconds”h]”hŒ‹The length of time of the window which the test
runs. That is, the test will run for â€œwidthâ€
microseconds per â€œwindowâ€ microseconds”…””}”(hjq*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mj	hjn*  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj\*  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Ml	hjí)  ubj“  )”}”(hX.  tracing_cpumask
When the test is started. A kernel thread is created that
runs the test. This thread will alternate between CPUs
listed in the tracing_cpumask between each period
(one "window"). To limit the test to specific CPUs
set the mask in this file to only the CPUs that the test
should run on.
”h]”(j™  )”}”(hŒtracing_cpumask”h]”hŒtracing_cpumask”…””}”(hj*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mt	hj‹*  ubj©  )”}”(hhh]”hÌ)”}”(hX  When the test is started. A kernel thread is created that
runs the test. This thread will alternate between CPUs
listed in the tracing_cpumask between each period
(one "window"). To limit the test to specific CPUs
set the mask in this file to only the CPUs that the test
should run on.”h]”hX!  When the test is started. A kernel thread is created that
runs the test. This thread will alternate between CPUs
listed in the tracing_cpumask between each period
(one â€œwindowâ€). To limit the test to specific CPUs
set the mask in this file to only the CPUs that the test
should run on.”…””}”(hj *  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mo	hj*  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj‹*  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´Mt	hjí)  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjé)  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M]	hjª(  h²hubeh}”(h]”Œhardware-latency-detector”ah ]”h"]”Œhardware latency detector”ah$]”h&]”uh1hµhh·h²hh³hÊh´M	ubh¶)”}”(hhh]”(h»)”}”(hŒfunction”h]”hŒfunction”…””}”(hjÑ*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÎ*  h²hh³hÊh´Mw	ubhÌ)”}”(hŒØThis tracer is the function tracer. Enabling the function tracer
can be done from the debug file system. Make sure the
ftrace_enabled is set; otherwise this tracer is a nop.
See the "ftrace_enabled" section below.
::”h]”hŒÙThis tracer is the function tracer. Enabling the function tracer
can be done from the debug file system. Make sure the
ftrace_enabled is set; otherwise this tracer is a nop.
See the â€œftrace_enabledâ€ section below.”…””}”(hjß*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´My	hjÎ*  h²hubj´  )”}”(hXÐ  # sysctl kernel.ftrace_enabled=1
# echo function > current_tracer
# echo 1 > tracing_on
# usleep 1
# echo 0 > tracing_on
# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 24799/24799   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1994  [002] ....  3082.063030: mutex_unlock <-rb_simple_write
            bash-1994  [002] ....  3082.063031: __mutex_unlock_slowpath <-mutex_unlock
            bash-1994  [002] ....  3082.063031: __fsnotify_parent <-fsnotify_modify
            bash-1994  [002] ....  3082.063032: fsnotify <-fsnotify_modify
            bash-1994  [002] ....  3082.063032: __srcu_read_lock <-fsnotify
            bash-1994  [002] ....  3082.063032: add_preempt_count <-__srcu_read_lock
            bash-1994  [002] ...1  3082.063032: sub_preempt_count <-__srcu_read_lock
            bash-1994  [002] ....  3082.063033: __srcu_read_unlock <-fsnotify
[...]”h]”hXÐ  # sysctl kernel.ftrace_enabled=1
# echo function > current_tracer
# echo 1 > tracing_on
# usleep 1
# echo 0 > tracing_on
# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 24799/24799   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1994  [002] ....  3082.063030: mutex_unlock <-rb_simple_write
            bash-1994  [002] ....  3082.063031: __mutex_unlock_slowpath <-mutex_unlock
            bash-1994  [002] ....  3082.063031: __fsnotify_parent <-fsnotify_modify
            bash-1994  [002] ....  3082.063032: fsnotify <-fsnotify_modify
            bash-1994  [002] ....  3082.063032: __srcu_read_lock <-fsnotify
            bash-1994  [002] ....  3082.063032: add_preempt_count <-__srcu_read_lock
            bash-1994  [002] ...1  3082.063032: sub_preempt_count <-__srcu_read_lock
            bash-1994  [002] ....  3082.063033: __srcu_read_unlock <-fsnotify
[...]”…””}”hjí*  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M	hjÎ*  h²hubhÌ)”}”(hX  Note: function tracer uses ring buffers to store the above
entries. The newest data may overwrite the oldest data.
Sometimes using echo to stop the trace is not sufficient because
the tracing could have overwritten the data that you wanted to
record. For this reason, it is sometimes better to disable
tracing directly from a program. This allows you to stop the
tracing at the point that you hit the part that you are
interested in. To disable the tracing directly from a C program,
something like following code snippet can be used::”h]”hX  Note: function tracer uses ring buffers to store the above
entries. The newest data may overwrite the oldest data.
Sometimes using echo to stop the trace is not sufficient because
the tracing could have overwritten the data that you wanted to
record. For this reason, it is sometimes better to disable
tracing directly from a program. This allows you to stop the
tracing at the point that you hit the part that you are
interested in. To disable the tracing directly from a C program,
something like following code snippet can be used:”…””}”(hjû*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M›	hjÎ*  h²hubj´  )”}”(hŒóint trace_fd;
[...]
int main(int argc, char *argv[]) {
        [...]
        trace_fd = open(tracing_file("tracing_on"), O_WRONLY);
        [...]
        if (condition_hit()) {
                write(trace_fd, "0", 1);
        }
        [...]
}”h]”hŒóint trace_fd;
[...]
int main(int argc, char *argv[]) {
        [...]
        trace_fd = open(tracing_file("tracing_on"), O_WRONLY);
        [...]
        if (condition_hit()) {
                write(trace_fd, "0", 1);
        }
        [...]
}”…””}”hj	+  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¥	hjÎ*  h²hubeh}”(h]”Œfunction”ah ]”h"]”Œfunction”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mw	ubh¶)”}”(hhh]”(h»)”}”(hŒSingle thread tracing”h]”hŒSingle thread tracing”…””}”(hj"+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj+  h²hh³hÊh´M³	ubhÌ)”}”(hŒKBy writing into set_ftrace_pid you can trace a
single thread. For example::”h]”hŒJBy writing into set_ftrace_pid you can trace a
single thread. For example:”…””}”(hj0+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mµ	hj+  h²hubj´  )”}”(hX  # cat set_ftrace_pid
no pid
# echo 3111 > set_ftrace_pid
# cat set_ftrace_pid
3111
# echo function > current_tracer
# cat trace | head
# tracer: function
#
#           TASK-PID    CPU#    TIMESTAMP  FUNCTION
#              | |       |          |         |
    yum-updatesd-3111  [003]  1637.254676: finish_task_switch <-thread_return
    yum-updatesd-3111  [003]  1637.254681: hrtimer_cancel <-schedule_hrtimeout_range
    yum-updatesd-3111  [003]  1637.254682: hrtimer_try_to_cancel <-hrtimer_cancel
    yum-updatesd-3111  [003]  1637.254683: lock_hrtimer_base <-hrtimer_try_to_cancel
    yum-updatesd-3111  [003]  1637.254685: fget_light <-do_sys_poll
    yum-updatesd-3111  [003]  1637.254686: pipe_poll <-do_sys_poll
# echo > set_ftrace_pid
# cat trace |head
# tracer: function
#
#           TASK-PID    CPU#    TIMESTAMP  FUNCTION
#              | |       |          |         |
##### CPU 3 buffer started ####
    yum-updatesd-3111  [003]  1701.957688: free_poll_entry <-poll_freewait
    yum-updatesd-3111  [003]  1701.957689: remove_wait_queue <-free_poll_entry
    yum-updatesd-3111  [003]  1701.957691: fput <-free_poll_entry
    yum-updatesd-3111  [003]  1701.957692: audit_syscall_exit <-sysret_audit
    yum-updatesd-3111  [003]  1701.957693: path_put <-audit_syscall_exit”h]”hX  # cat set_ftrace_pid
no pid
# echo 3111 > set_ftrace_pid
# cat set_ftrace_pid
3111
# echo function > current_tracer
# cat trace | head
# tracer: function
#
#           TASK-PID    CPU#    TIMESTAMP  FUNCTION
#              | |       |          |         |
    yum-updatesd-3111  [003]  1637.254676: finish_task_switch <-thread_return
    yum-updatesd-3111  [003]  1637.254681: hrtimer_cancel <-schedule_hrtimeout_range
    yum-updatesd-3111  [003]  1637.254682: hrtimer_try_to_cancel <-hrtimer_cancel
    yum-updatesd-3111  [003]  1637.254683: lock_hrtimer_base <-hrtimer_try_to_cancel
    yum-updatesd-3111  [003]  1637.254685: fget_light <-do_sys_poll
    yum-updatesd-3111  [003]  1637.254686: pipe_poll <-do_sys_poll
# echo > set_ftrace_pid
# cat trace |head
# tracer: function
#
#           TASK-PID    CPU#    TIMESTAMP  FUNCTION
#              | |       |          |         |
##### CPU 3 buffer started ####
    yum-updatesd-3111  [003]  1701.957688: free_poll_entry <-poll_freewait
    yum-updatesd-3111  [003]  1701.957689: remove_wait_queue <-free_poll_entry
    yum-updatesd-3111  [003]  1701.957691: fput <-free_poll_entry
    yum-updatesd-3111  [003]  1701.957692: audit_syscall_exit <-sysret_audit
    yum-updatesd-3111  [003]  1701.957693: path_put <-audit_syscall_exit”…””}”hj>+  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¸	hj+  h²hubhÌ)”}”(hŒdIf you want to trace a function when executing, you could use
something like this simple program.
::”h]”hŒaIf you want to trace a function when executing, you could use
something like this simple program.”…””}”(hjL+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÖ	hj+  h²hubj´  )”}”(hX‰  #include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <string.h>

#define _STR(x) #x
#define STR(x) _STR(x)
#define MAX_PATH 256

const char *find_tracefs(void)
{
       static char tracefs[MAX_PATH+1];
       static int tracefs_found;
       char type[100];
       FILE *fp;

       if (tracefs_found)
               return tracefs;

       if ((fp = fopen("/proc/mounts","r")) == NULL) {
               perror("/proc/mounts");
               return NULL;
       }

       while (fscanf(fp, "%*s %"
                     STR(MAX_PATH)
                     "s %99s %*s %*d %*d\n",
                     tracefs, type) == 2) {
               if (strcmp(type, "tracefs") == 0)
                       break;
       }
       fclose(fp);

       if (strcmp(type, "tracefs") != 0) {
               fprintf(stderr, "tracefs not mounted");
               return NULL;
       }

       strcat(tracefs, "/tracing/");
       tracefs_found = 1;

       return tracefs;
}

const char *tracing_file(const char *file_name)
{
       static char trace_file[MAX_PATH+1];
       snprintf(trace_file, MAX_PATH, "%s/%s", find_tracefs(), file_name);
       return trace_file;
}

int main (int argc, char **argv)
{
        if (argc < 1)
                exit(-1);

        if (fork() > 0) {
                int fd, ffd;
                char line[64];
                int s;

                ffd = open(tracing_file("current_tracer"), O_WRONLY);
                if (ffd < 0)
                        exit(-1);
                write(ffd, "nop", 3);

                fd = open(tracing_file("set_ftrace_pid"), O_WRONLY);
                s = sprintf(line, "%d\n", getpid());
                write(fd, line, s);

                write(ffd, "function", 8);

                close(fd);
                close(ffd);

                execvp(argv[1], argv+1);
        }

        return 0;
}”h]”hX‰  #include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <string.h>

#define _STR(x) #x
#define STR(x) _STR(x)
#define MAX_PATH 256

const char *find_tracefs(void)
{
       static char tracefs[MAX_PATH+1];
       static int tracefs_found;
       char type[100];
       FILE *fp;

       if (tracefs_found)
               return tracefs;

       if ((fp = fopen("/proc/mounts","r")) == NULL) {
               perror("/proc/mounts");
               return NULL;
       }

       while (fscanf(fp, "%*s %"
                     STR(MAX_PATH)
                     "s %99s %*s %*d %*d\n",
                     tracefs, type) == 2) {
               if (strcmp(type, "tracefs") == 0)
                       break;
       }
       fclose(fp);

       if (strcmp(type, "tracefs") != 0) {
               fprintf(stderr, "tracefs not mounted");
               return NULL;
       }

       strcat(tracefs, "/tracing/");
       tracefs_found = 1;

       return tracefs;
}

const char *tracing_file(const char *file_name)
{
       static char trace_file[MAX_PATH+1];
       snprintf(trace_file, MAX_PATH, "%s/%s", find_tracefs(), file_name);
       return trace_file;
}

int main (int argc, char **argv)
{
        if (argc < 1)
                exit(-1);

        if (fork() > 0) {
                int fd, ffd;
                char line[64];
                int s;

                ffd = open(tracing_file("current_tracer"), O_WRONLY);
                if (ffd < 0)
                        exit(-1);
                write(ffd, "nop", 3);

                fd = open(tracing_file("set_ftrace_pid"), O_WRONLY);
                s = sprintf(line, "%d\n", getpid());
                write(fd, line, s);

                write(ffd, "function", 8);

                close(fd);
                close(ffd);

                execvp(argv[1], argv+1);
        }

        return 0;
}”…””}”hjZ+  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÚ	hj+  h²hubhÌ)”}”(hŒOr this simple script!
::”h]”hŒOr this simple script!”…””}”(hjh+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M.
hj+  h²hubj´  )”}”(hŒÜ#!/bin/bash

tracefs=`sed -ne 's/^tracefs \(.*\) tracefs.*/\1/p' /proc/mounts`
echo 0 > $tracefs/tracing_on
echo $$ > $tracefs/set_ftrace_pid
echo function > $tracefs/current_tracer
echo 1 > $tracefs/tracing_on
exec "$@"”h]”hŒÜ#!/bin/bash

tracefs=`sed -ne 's/^tracefs \(.*\) tracefs.*/\1/p' /proc/mounts`
echo 0 > $tracefs/tracing_on
echo $$ > $tracefs/set_ftrace_pid
echo function > $tracefs/current_tracer
echo 1 > $tracefs/tracing_on
exec "$@"”…””}”hjv+  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M1
hj+  h²hubeh}”(h]”Œsingle-thread-tracing”ah ]”h"]”Œsingle thread tracing”ah$]”h&]”uh1hµhh·h²hh³hÊh´M³	ubh¶)”}”(hhh]”(h»)”}”(hŒfunction graph tracer”h]”hŒfunction graph tracer”…””}”(hj+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjŒ+  h²hh³hÊh´M<
ubhÌ)”}”(hXŽ  This tracer is similar to the function tracer except that it
probes a function on its entry and its exit. This is done by
using a dynamically allocated stack of return addresses in each
task_struct. On function entry the tracer overwrites the return
address of each function traced to set a custom probe. Thus the
original return address is stored on the stack of return address
in the task_struct.”h]”hXŽ  This tracer is similar to the function tracer except that it
probes a function on its entry and its exit. This is done by
using a dynamically allocated stack of return addresses in each
task_struct. On function entry the tracer overwrites the return
address of each function traced to set a custom probe. Thus the
original return address is stored on the stack of return address
in the task_struct.”…””}”(hj+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M>
hjŒ+  h²hubhÌ)”}”(hŒEProbing on both ends of a function leads to special features
such as:”h]”hŒEProbing on both ends of a function leads to special features
such as:”…””}”(hj«+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MF
hjŒ+  h²hubj  )”}”(hhh]”(j”  )”}”(hŒ&measure of a function's time execution”h]”hÌ)”}”(hj¾+  h]”hŒ(measure of a functionâ€™s time execution”…””}”(hjÀ+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MI
hj¼+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¹+  h²hh³hÊh´Nubj”  )”}”(hŒ:having a reliable call stack to draw function calls graph
”h]”hÌ)”}”(hŒ9having a reliable call stack to draw function calls graph”h]”hŒ9having a reliable call stack to draw function calls graph”…””}”(hj×+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MJ
hjÓ+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¹+  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´MI
hjŒ+  h²hubhÌ)”}”(hŒ,This tracer is useful in several situations:”h]”hŒ,This tracer is useful in several situations:”…””}”(hjñ+  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´ML
hjŒ+  h²hubj  )”}”(hhh]”(j”  )”}”(hŒyou want to find the reason of a strange kernel behavior and
need to see what happens in detail on any areas (or specific
ones).
”h]”hÌ)”}”(hŒ€you want to find the reason of a strange kernel behavior and
need to see what happens in detail on any areas (or specific
ones).”h]”hŒ€you want to find the reason of a strange kernel behavior and
need to see what happens in detail on any areas (or specific
ones).”…””}”(hj,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MN
hj,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjÿ+  h²hh³hÊh´Nubj”  )”}”(hŒLyou are experiencing weird latencies but it's difficult to
find its origin.
”h]”hÌ)”}”(hŒKyou are experiencing weird latencies but it's difficult to
find its origin.”h]”hŒMyou are experiencing weird latencies but itâ€™s difficult to
find its origin.”…””}”(hj,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MR
hj,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjÿ+  h²hh³hÊh´Nubj”  )”}”(hŒDyou want to find quickly which path is taken by a specific
function
”h]”hÌ)”}”(hŒCyou want to find quickly which path is taken by a specific
function”h]”hŒCyou want to find quickly which path is taken by a specific
function”…””}”(hj6,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MU
hj2,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjÿ+  h²hh³hÊh´Nubj”  )”}”(hŒRyou just want to peek inside a working kernel and want to see
what happens there.
”h]”hÌ)”}”(hŒQyou just want to peek inside a working kernel and want to see
what happens there.”h]”hŒQyou just want to peek inside a working kernel and want to see
what happens there.”…””}”(hjN,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MX
hjJ,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjÿ+  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´MN
hjŒ+  h²hubj´  )”}”(hXî  # tracer: function_graph
#
# CPU  DURATION                  FUNCTION CALLS
# |     |   |                     |   |   |   |

 0)               |  sys_open() {
 0)               |    do_sys_open() {
 0)               |      getname() {
 0)               |        kmem_cache_alloc() {
 0)   1.382 us    |          __might_sleep();
 0)   2.478 us    |        }
 0)               |        strncpy_from_user() {
 0)               |          might_fault() {
 0)   1.389 us    |            __might_sleep();
 0)   2.553 us    |          }
 0)   3.807 us    |        }
 0)   7.876 us    |      }
 0)               |      alloc_fd() {
 0)   0.668 us    |        _spin_lock();
 0)   0.570 us    |        expand_files();
 0)   0.586 us    |        _spin_unlock();”h]”h•á     Xî  # tracer: function_graph
#
# CPU  DURATION                  FUNCTION CALLS
# |     |   |                     |   |   |   |

 0)               |  sys_open() {
 0)               |    do_sys_open() {
 0)               |      getname() {
 0)               |        kmem_cache_alloc() {
 0)   1.382 us    |          __might_sleep();
 0)   2.478 us    |        }
 0)               |        strncpy_from_user() {
 0)               |          might_fault() {
 0)   1.389 us    |            __might_sleep();
 0)   2.553 us    |          }
 0)   3.807 us    |        }
 0)   7.876 us    |      }
 0)               |      alloc_fd() {
 0)   0.668 us    |        _spin_lock();
 0)   0.570 us    |        expand_files();
 0)   0.586 us    |        _spin_unlock();”…””}”hjh,  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M]
hjŒ+  h²hubhÌ)”}”(hŒThere are several columns that can be dynamically
enabled/disabled. You can use every combination of options you
want, depending on your needs.”h]”hŒThere are several columns that can be dynamically
enabled/disabled. You can use every combination of options you
want, depending on your needs.”…””}”(hjv,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mt
hjŒ+  h²hubj  )”}”(hhh]”(j”  )”}”(hX>  The cpu number on which the function executed is default
enabled.  It is sometimes better to only trace one cpu (see
tracing_cpumask file) or you might sometimes see unordered
function calls while cpu tracing switch.

      - hide: echo nofuncgraph-cpu > trace_options
      - show: echo funcgraph-cpu > trace_options
”h]”(hÌ)”}”(hŒØThe cpu number on which the function executed is default
enabled.  It is sometimes better to only trace one cpu (see
tracing_cpumask file) or you might sometimes see unordered
function calls while cpu tracing switch.”h]”hŒØThe cpu number on which the function executed is default
enabled.  It is sometimes better to only trace one cpu (see
tracing_cpumask file) or you might sometimes see unordered
function calls while cpu tracing switch.”…””}”(hj‹,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mx
hj‡,  ubjh  )”}”(hŒX- hide: echo nofuncgraph-cpu > trace_options
- show: echo funcgraph-cpu > trace_options
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ*hide: echo nofuncgraph-cpu > trace_options”h]”hÌ)”}”(hj¢,  h]”hŒ*hide: echo nofuncgraph-cpu > trace_options”…””}”(hj¤,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M}
hj ,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj,  ubj”  )”}”(hŒ)show: echo funcgraph-cpu > trace_options
”h]”hÌ)”}”(hŒ(show: echo funcgraph-cpu > trace_options”h]”hŒ(show: echo funcgraph-cpu > trace_options”…””}”(hj»,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M~
hj·,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj,  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´M}
hj™,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M}
hj‡,  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj„,  h²hh³hÊh´Nubj”  )”}”(hX.  The duration (function's time of execution) is displayed on
the closing bracket line of a function or on the same line
than the current function in case of a leaf one. It is default
enabled.

      - hide: echo nofuncgraph-duration > trace_options
      - show: echo funcgraph-duration > trace_options
”h]”(hÌ)”}”(hŒ¾The duration (function's time of execution) is displayed on
the closing bracket line of a function or on the same line
than the current function in case of a leaf one. It is default
enabled.”h]”hŒÀThe duration (functionâ€™s time of execution) is displayed on
the closing bracket line of a function or on the same line
than the current function in case of a leaf one. It is default
enabled.”…””}”(hjå,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M€
hjá,  ubjh  )”}”(hŒb- hide: echo nofuncgraph-duration > trace_options
- show: echo funcgraph-duration > trace_options
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ/hide: echo nofuncgraph-duration > trace_options”h]”hÌ)”}”(hjü,  h]”hŒ/hide: echo nofuncgraph-duration > trace_options”…””}”(hjþ,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M…
hjú,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj÷,  ubj”  )”}”(hŒ.show: echo funcgraph-duration > trace_options
”h]”hÌ)”}”(hŒ-show: echo funcgraph-duration > trace_options”h]”hŒ-show: echo funcgraph-duration > trace_options”…””}”(hj-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M†
hj-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj÷,  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´M…
hjó,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M…
hjá,  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj„,  h²hh³hÊh´Nubj”  )”}”(hXæ  The overhead field precedes the duration field in case of
reached duration thresholds.

      - hide: echo nofuncgraph-overhead > trace_options
      - show: echo funcgraph-overhead > trace_options
      - depends on: funcgraph-duration

ie::

  3) # 1837.709 us |          } /* __switch_to */
  3)               |          finish_task_switch() {
  3)   0.313 us    |            _raw_spin_unlock_irq();
  3)   3.177 us    |          }
  3) # 1889.063 us |        } /* __schedule */
  3) ! 140.417 us  |      } /* __schedule */
  3) # 2034.948 us |    } /* schedule */
  3) * 33998.59 us |  } /* schedule_preempt_disabled */

  [...]

  1)   0.260 us    |              msecs_to_jiffies();
  1)   0.313 us    |              __rcu_read_unlock();
  1) + 61.770 us   |            }
  1) + 64.479 us   |          }
  1)   0.313 us    |          rcu_bh_qs();
  1)   0.313 us    |          __local_bh_enable();
  1) ! 217.240 us  |        }
  1)   0.365 us    |        idle_cpu();
  1)               |        rcu_irq_exit() {
  1)   0.417 us    |          rcu_eqs_enter_common.isra.47();
  1)   3.125 us    |        }
  1) ! 227.812 us  |      }
  1) ! 457.395 us  |    }
  1) @ 119760.2 us |  }

  [...]

  2)               |    handle_IPI() {
  1)   6.979 us    |                  }
  2)   0.417 us    |      scheduler_ipi();
  1)   9.791 us    |                }
  1) + 12.917 us   |              }
  2)   3.490 us    |    }
  1) + 15.729 us   |            }
  1) + 18.542 us   |          }
  2) $ 3594274 us  |  }
”h]”(hÌ)”}”(hŒVThe overhead field precedes the duration field in case of
reached duration thresholds.”h]”hŒVThe overhead field precedes the duration field in case of
reached duration thresholds.”…””}”(hj?-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mˆ
hj;-  ubjh  )”}”(hŒƒ- hide: echo nofuncgraph-overhead > trace_options
- show: echo funcgraph-overhead > trace_options
- depends on: funcgraph-duration
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ/hide: echo nofuncgraph-overhead > trace_options”h]”hÌ)”}”(hjV-  h]”hŒ/hide: echo nofuncgraph-overhead > trace_options”…””}”(hjX-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‹
hjT-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjQ-  ubj”  )”}”(hŒ-show: echo funcgraph-overhead > trace_options”h]”hÌ)”}”(hjm-  h]”hŒ-show: echo funcgraph-overhead > trace_options”…””}”(hjo-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŒ
hjk-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjQ-  ubj”  )”}”(hŒdepends on: funcgraph-duration
”h]”hÌ)”}”(hŒdepends on: funcgraph-duration”h]”hŒdepends on: funcgraph-duration”…””}”(hj†-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M
hj‚-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjQ-  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´M‹
hjM-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M‹
hj;-  ubhÌ)”}”(hŒie::”h]”hŒie:”…””}”(hj¦-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M
hj;-  ubj´  )”}”(hX¯  3) # 1837.709 us |          } /* __switch_to */
3)               |          finish_task_switch() {
3)   0.313 us    |            _raw_spin_unlock_irq();
3)   3.177 us    |          }
3) # 1889.063 us |        } /* __schedule */
3) ! 140.417 us  |      } /* __schedule */
3) # 2034.948 us |    } /* schedule */
3) * 33998.59 us |  } /* schedule_preempt_disabled */

[...]

1)   0.260 us    |              msecs_to_jiffies();
1)   0.313 us    |              __rcu_read_unlock();
1) + 61.770 us   |            }
1) + 64.479 us   |          }
1)   0.313 us    |          rcu_bh_qs();
1)   0.313 us    |          __local_bh_enable();
1) ! 217.240 us  |        }
1)   0.365 us    |        idle_cpu();
1)               |        rcu_irq_exit() {
1)   0.417 us    |          rcu_eqs_enter_common.isra.47();
1)   3.125 us    |        }
1) ! 227.812 us  |      }
1) ! 457.395 us  |    }
1) @ 119760.2 us |  }

[...]

2)               |    handle_IPI() {
1)   6.979 us    |                  }
2)   0.417 us    |      scheduler_ipi();
1)   9.791 us    |                }
1) + 12.917 us   |              }
2)   3.490 us    |    }
1) + 15.729 us   |            }
1) + 18.542 us   |          }
2) $ 3594274 us  |  }”h]”hX¯  3) # 1837.709 us |          } /* __switch_to */
3)               |          finish_task_switch() {
3)   0.313 us    |            _raw_spin_unlock_irq();
3)   3.177 us    |          }
3) # 1889.063 us |        } /* __schedule */
3) ! 140.417 us  |      } /* __schedule */
3) # 2034.948 us |    } /* schedule */
3) * 33998.59 us |  } /* schedule_preempt_disabled */

[...]

1)   0.260 us    |              msecs_to_jiffies();
1)   0.313 us    |              __rcu_read_unlock();
1) + 61.770 us   |            }
1) + 64.479 us   |          }
1)   0.313 us    |          rcu_bh_qs();
1)   0.313 us    |          __local_bh_enable();
1) ! 217.240 us  |        }
1)   0.365 us    |        idle_cpu();
1)               |        rcu_irq_exit() {
1)   0.417 us    |          rcu_eqs_enter_common.isra.47();
1)   3.125 us    |        }
1) ! 227.812 us  |      }
1) ! 457.395 us  |    }
1) @ 119760.2 us |  }

[...]

2)               |    handle_IPI() {
1)   6.979 us    |                  }
2)   0.417 us    |      scheduler_ipi();
1)   9.791 us    |                }
1) + 12.917 us   |              }
2)   3.490 us    |    }
1) + 15.729 us   |            }
1) + 18.542 us   |          }
2) $ 3594274 us  |  }”…””}”hj´-  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M‘
hj;-  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj„,  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´Mx
hjŒ+  h²hubhÌ)”}”(hŒFlags::”h]”hŒFlags:”…””}”(hjÎ-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M·
hjŒ+  h²hubj´  )”}”(hX  + means that the function exceeded 10 usecs.
! means that the function exceeded 100 usecs.
# means that the function exceeded 1000 usecs.
* means that the function exceeded 10 msecs.
@ means that the function exceeded 100 msecs.
$ means that the function exceeded 1 sec.”h]”hX  + means that the function exceeded 10 usecs.
! means that the function exceeded 100 usecs.
# means that the function exceeded 1000 usecs.
* means that the function exceeded 10 msecs.
@ means that the function exceeded 100 msecs.
$ means that the function exceeded 1 sec.”…””}”hjÜ-  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¹
hjŒ+  h²hubj  )”}”(hhh]”(j”  )”}”(hXæ  The task/pid field displays the thread cmdline and pid which
executed the function. It is default disabled.

      - hide: echo nofuncgraph-proc > trace_options
      - show: echo funcgraph-proc > trace_options

ie::

  # tracer: function_graph
  #
  # CPU  TASK/PID        DURATION                  FUNCTION CALLS
  # |    |    |           |   |                     |   |   |   |
  0)    sh-4802     |               |                  d_free() {
  0)    sh-4802     |               |                    call_rcu() {
  0)    sh-4802     |               |                      __call_rcu() {
  0)    sh-4802     |   0.616 us    |                        rcu_process_gp_end();
  0)    sh-4802     |   0.586 us    |                        check_for_new_grace_period();
  0)    sh-4802     |   2.899 us    |                      }
  0)    sh-4802     |   4.040 us    |                    }
  0)    sh-4802     |   5.151 us    |                  }
  0)    sh-4802     | + 49.370 us   |                }

”h]”(hÌ)”}”(hŒkThe task/pid field displays the thread cmdline and pid which
executed the function. It is default disabled.”h]”hŒkThe task/pid field displays the thread cmdline and pid which
executed the function. It is default disabled.”…””}”(hjñ-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÁ
hjí-  ubjh  )”}”(hŒZ- hide: echo nofuncgraph-proc > trace_options
- show: echo funcgraph-proc > trace_options
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ+hide: echo nofuncgraph-proc > trace_options”h]”hÌ)”}”(hj.  h]”hŒ+hide: echo nofuncgraph-proc > trace_options”…””}”(hj
.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÄ
hj.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj.  ubj”  )”}”(hŒ*show: echo funcgraph-proc > trace_options
”h]”hÌ)”}”(hŒ)show: echo funcgraph-proc > trace_options”h]”hŒ)show: echo funcgraph-proc > trace_options”…””}”(hj!.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÅ
hj.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj.  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´MÄ
hjÿ-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÄ
hjí-  ubhÌ)”}”(hŒie::”h]”hŒie:”…””}”(hjA.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÇ
hjí-  ubj´  )”}”(hXð  # tracer: function_graph
#
# CPU  TASK/PID        DURATION                  FUNCTION CALLS
# |    |    |           |   |                     |   |   |   |
0)    sh-4802     |               |                  d_free() {
0)    sh-4802     |               |                    call_rcu() {
0)    sh-4802     |               |                      __call_rcu() {
0)    sh-4802     |   0.616 us    |                        rcu_process_gp_end();
0)    sh-4802     |   0.586 us    |                        check_for_new_grace_period();
0)    sh-4802     |   2.899 us    |                      }
0)    sh-4802     |   4.040 us    |                    }
0)    sh-4802     |   5.151 us    |                  }
0)    sh-4802     | + 49.370 us   |                }”h]”hXð  # tracer: function_graph
#
# CPU  TASK/PID        DURATION                  FUNCTION CALLS
# |    |    |           |   |                     |   |   |   |
0)    sh-4802     |               |                  d_free() {
0)    sh-4802     |               |                    call_rcu() {
0)    sh-4802     |               |                      __call_rcu() {
0)    sh-4802     |   0.616 us    |                        rcu_process_gp_end();
0)    sh-4802     |   0.586 us    |                        check_for_new_grace_period();
0)    sh-4802     |   2.899 us    |                      }
0)    sh-4802     |   4.040 us    |                    }
0)    sh-4802     |   5.151 us    |                  }
0)    sh-4802     | + 49.370 us   |                }”…””}”hjO.  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÉ
hjí-  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjê-  h²hh³hÊh´Nubj”  )”}”(hXë  The absolute time field is an absolute timestamp given by the
system clock since it started. A snapshot of this time is
given on each entry/exit of functions

      - hide: echo nofuncgraph-abstime > trace_options
      - show: echo funcgraph-abstime > trace_options

ie::

  #
  #      TIME       CPU  DURATION                  FUNCTION CALLS
  #       |         |     |   |                     |   |   |   |
  360.774522 |   1)   0.541 us    |                                          }
  360.774522 |   1)   4.663 us    |                                        }
  360.774523 |   1)   0.541 us    |                                        __wake_up_bit();
  360.774524 |   1)   6.796 us    |                                      }
  360.774524 |   1)   7.952 us    |                                    }
  360.774525 |   1)   9.063 us    |                                  }
  360.774525 |   1)   0.615 us    |                                  journal_mark_dirty();
  360.774527 |   1)   0.578 us    |                                  __brelse();
  360.774528 |   1)               |                                  reiserfs_prepare_for_journal() {
  360.774528 |   1)               |                                    unlock_buffer() {
  360.774529 |   1)               |                                      wake_up_bit() {
  360.774529 |   1)               |                                        bit_waitqueue() {
  360.774530 |   1)   0.594 us    |                                          __phys_addr();

”h]”(hÌ)”}”(hŒThe absolute time field is an absolute timestamp given by the
system clock since it started. A snapshot of this time is
given on each entry/exit of functions”h]”hŒThe absolute time field is an absolute timestamp given by the
system clock since it started. A snapshot of this time is
given on each entry/exit of functions”…””}”(hjg.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MØ
hjc.  ubjh  )”}”(hŒ`- hide: echo nofuncgraph-abstime > trace_options
- show: echo funcgraph-abstime > trace_options
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ.hide: echo nofuncgraph-abstime > trace_options”h]”hÌ)”}”(hj~.  h]”hŒ.hide: echo nofuncgraph-abstime > trace_options”…””}”(hj€.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÜ
hj|.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjy.  ubj”  )”}”(hŒ-show: echo funcgraph-abstime > trace_options
”h]”hÌ)”}”(hŒ,show: echo funcgraph-abstime > trace_options”h]”hŒ,show: echo funcgraph-abstime > trace_options”…””}”(hj—.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÝ
hj“.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjy.  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´MÜ
hju.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÜ
hjc.  ubhÌ)”}”(hŒie::”h]”hŒie:”…””}”(hj·.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mß
hjc.  ubj´  )”}”(hX·  #
#      TIME       CPU  DURATION                  FUNCTION CALLS
#       |         |     |   |                     |   |   |   |
360.774522 |   1)   0.541 us    |                                          }
360.774522 |   1)   4.663 us    |                                        }
360.774523 |   1)   0.541 us    |                                        __wake_up_bit();
360.774524 |   1)   6.796 us    |                                      }
360.774524 |   1)   7.952 us    |                                    }
360.774525 |   1)   9.063 us    |                                  }
360.774525 |   1)   0.615 us    |                                  journal_mark_dirty();
360.774527 |   1)   0.578 us    |                                  __brelse();
360.774528 |   1)               |                                  reiserfs_prepare_for_journal() {
360.774528 |   1)               |                                    unlock_buffer() {
360.774529 |   1)               |                                      wake_up_bit() {
360.774529 |   1)               |                                        bit_waitqueue() {
360.774530 |   1)   0.594 us    |                                          __phys_addr();”h]”hX·  #
#      TIME       CPU  DURATION                  FUNCTION CALLS
#       |         |     |   |                     |   |   |   |
360.774522 |   1)   0.541 us    |                                          }
360.774522 |   1)   4.663 us    |                                        }
360.774523 |   1)   0.541 us    |                                        __wake_up_bit();
360.774524 |   1)   6.796 us    |                                      }
360.774524 |   1)   7.952 us    |                                    }
360.774525 |   1)   9.063 us    |                                  }
360.774525 |   1)   0.615 us    |                                  journal_mark_dirty();
360.774527 |   1)   0.578 us    |                                  __brelse();
360.774528 |   1)               |                                  reiserfs_prepare_for_journal() {
360.774528 |   1)               |                                    unlock_buffer() {
360.774529 |   1)               |                                      wake_up_bit() {
360.774529 |   1)               |                                        bit_waitqueue() {
360.774530 |   1)   0.594 us    |                                          __phys_addr();”…””}”hjÅ.  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Má
hjc.  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hjê-  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´MÁ
hjŒ+  h²hubhÌ)”}”(hŒˆThe function name is always displayed after the closing bracket
for a function if the start of that function is not in the
trace buffer.”h]”hŒˆThe function name is always displayed after the closing bracket
for a function if the start of that function is not in the
trace buffer.”…””}”(hjß.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mó
hjŒ+  h²hubhÌ)”}”(hŒËDisplay of the function name after the closing bracket may be
enabled for functions whose start is in the trace buffer,
allowing easier searching with grep for function durations.
It is default disabled.”h]”hŒËDisplay of the function name after the closing bracket may be
enabled for functions whose start is in the trace buffer,
allowing easier searching with grep for function durations.
It is default disabled.”…””}”(hjí.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M÷
hjŒ+  h²hubjh  )”}”(hXT        - hide: echo nofuncgraph-tail > trace_options
      - show: echo funcgraph-tail > trace_options

Example with nofuncgraph-tail (default)::

  0)               |      putname() {
  0)               |        kmem_cache_free() {
  0)   0.518 us    |          __phys_addr();
  0)   1.757 us    |        }
  0)   2.861 us    |      }

Example with funcgraph-tail::

  0)               |      putname() {
  0)               |        kmem_cache_free() {
  0)   0.518 us    |          __phys_addr();
  0)   1.757 us    |        } /* kmem_cache_free() */
  0)   2.861 us    |      } /* putname() */
”h]”(jh  )”}”(hŒZ- hide: echo nofuncgraph-tail > trace_options
- show: echo funcgraph-tail > trace_options
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ+hide: echo nofuncgraph-tail > trace_options”h]”hÌ)”}”(hj/  h]”hŒ+hide: echo nofuncgraph-tail > trace_options”…””}”(hj
/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mü
hj/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj/  ubj”  )”}”(hŒ*show: echo funcgraph-tail > trace_options
”h]”hÌ)”}”(hŒ)show: echo funcgraph-tail > trace_options”h]”hŒ)show: echo funcgraph-tail > trace_options”…””}”(hj!/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mý
hj/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj/  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´Mü
hjÿ.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mü
hjû.  ubhÌ)”}”(hŒ)Example with nofuncgraph-tail (default)::”h]”hŒ(Example with nofuncgraph-tail (default):”…””}”(hjA/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mÿ
hjû.  ubj´  )”}”(hŒ²0)               |      putname() {
0)               |        kmem_cache_free() {
0)   0.518 us    |          __phys_addr();
0)   1.757 us    |        }
0)   2.861 us    |      }”h]”hŒ²0)               |      putname() {
0)               |        kmem_cache_free() {
0)   0.518 us    |          __phys_addr();
0)   1.757 us    |        }
0)   2.861 us    |      }”…””}”hjO/  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhjû.  ubhÌ)”}”(hŒExample with funcgraph-tail::”h]”hŒExample with funcgraph-tail:”…””}”(hj]/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjû.  ubj´  )”}”(hŒÚ0)               |      putname() {
0)               |        kmem_cache_free() {
0)   0.518 us    |          __phys_addr();
0)   1.757 us    |        } /* kmem_cache_free() */
0)   2.861 us    |      } /* putname() */”h]”hŒÚ0)               |      putname() {
0)               |        kmem_cache_free() {
0)   0.518 us    |          __phys_addr();
0)   1.757 us    |        } /* kmem_cache_free() */
0)   2.861 us    |      } /* putname() */”…””}”hjk/  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M	hjû.  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mü
hjŒ+  h²hubhÌ)”}”(hŒÒThe return value of each traced function can be displayed after
an equal sign "=". When encountering system call failures, it
can be very helpful to quickly locate the function that first
returns an error code.”h]”hŒÖThe return value of each traced function can be displayed after
an equal sign â€œ=â€. When encountering system call failures, it
can be very helpful to quickly locate the function that first
returns an error code.”…””}”(hj/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjŒ+  h²hubjh  )”}”(hX@        - hide: echo nofuncgraph-retval > trace_options
      - show: echo funcgraph-retval > trace_options

Example with funcgraph-retval::

  1)               |    cgroup_migrate() {
  1)   0.651 us    |      cgroup_migrate_add_task(); /* = 0xffff93fcfd346c00 */
  1)               |      cgroup_migrate_execute() {
  1)               |        cpu_cgroup_can_attach() {
  1)               |          cgroup_taskset_first() {
  1)   0.732 us    |            cgroup_taskset_next(); /* = 0xffff93fc8fb20000 */
  1)   1.232 us    |          } /* cgroup_taskset_first = 0xffff93fc8fb20000 */
  1)   0.380 us    |          sched_rt_can_attach(); /* = 0x0 */
  1)   2.335 us    |        } /* cpu_cgroup_can_attach = -22 */
  1)   4.369 us    |      } /* cgroup_migrate_execute = -22 */
  1)   7.143 us    |    } /* cgroup_migrate = -22 */
”h]”(jh  )”}”(hŒ^- hide: echo nofuncgraph-retval > trace_options
- show: echo funcgraph-retval > trace_options
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ-hide: echo nofuncgraph-retval > trace_options”h]”hÌ)”}”(hjš/  h]”hŒ-hide: echo nofuncgraph-retval > trace_options”…””}”(hjœ/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj˜/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj•/  ubj”  )”}”(hŒ,show: echo funcgraph-retval > trace_options
”h]”hÌ)”}”(hŒ+show: echo funcgraph-retval > trace_options”h]”hŒ+show: echo funcgraph-retval > trace_options”…””}”(hj³/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj¯/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj•/  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´Mhj‘/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj/  ubhÌ)”}”(hŒExample with funcgraph-retval::”h]”hŒExample with funcgraph-retval:”…””}”(hjÓ/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj/  ubj´  )”}”(hX  1)               |    cgroup_migrate() {
1)   0.651 us    |      cgroup_migrate_add_task(); /* = 0xffff93fcfd346c00 */
1)               |      cgroup_migrate_execute() {
1)               |        cpu_cgroup_can_attach() {
1)               |          cgroup_taskset_first() {
1)   0.732 us    |            cgroup_taskset_next(); /* = 0xffff93fc8fb20000 */
1)   1.232 us    |          } /* cgroup_taskset_first = 0xffff93fc8fb20000 */
1)   0.380 us    |          sched_rt_can_attach(); /* = 0x0 */
1)   2.335 us    |        } /* cpu_cgroup_can_attach = -22 */
1)   4.369 us    |      } /* cgroup_migrate_execute = -22 */
1)   7.143 us    |    } /* cgroup_migrate = -22 */”h]”hX  1)               |    cgroup_migrate() {
1)   0.651 us    |      cgroup_migrate_add_task(); /* = 0xffff93fcfd346c00 */
1)               |      cgroup_migrate_execute() {
1)               |        cpu_cgroup_can_attach() {
1)               |          cgroup_taskset_first() {
1)   0.732 us    |            cgroup_taskset_next(); /* = 0xffff93fc8fb20000 */
1)   1.232 us    |          } /* cgroup_taskset_first = 0xffff93fc8fb20000 */
1)   0.380 us    |          sched_rt_can_attach(); /* = 0x0 */
1)   2.335 us    |        } /* cpu_cgroup_can_attach = -22 */
1)   4.369 us    |      } /* cgroup_migrate_execute = -22 */
1)   7.143 us    |    } /* cgroup_migrate = -22 */”…””}”hjá/  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhj/  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MhjŒ+  h²hubhÌ)”}”(hŒ¦The above example shows that the function cpu_cgroup_can_attach
returned the error code -22 firstly, then we can read the code
of this function to get the root cause.”h]”hŒ¦The above example shows that the function cpu_cgroup_can_attach
returned the error code -22 firstly, then we can read the code
of this function to get the root cause.”…””}”(hjõ/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M%hjŒ+  h²hubhÌ)”}”(hŒæWhen the option funcgraph-retval-hex is not set, the return value can
be displayed in a smart way. Specifically, if it is an error code,
it will be printed in signed decimal format, otherwise it will
printed in hexadecimal format.”h]”hŒæWhen the option funcgraph-retval-hex is not set, the return value can
be displayed in a smart way. Specifically, if it is an error code,
it will be printed in signed decimal format, otherwise it will
printed in hexadecimal format.”…””}”(hj0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M)hjŒ+  h²hubjh  )”}”(hX        - smart: echo nofuncgraph-retval-hex > trace_options
      - hexadecimal: echo funcgraph-retval-hex > trace_options

Example with funcgraph-retval-hex::

  1)               |      cgroup_migrate() {
  1)   0.651 us    |        cgroup_migrate_add_task(); /* = 0xffff93fcfd346c00 */
  1)               |        cgroup_migrate_execute() {
  1)               |          cpu_cgroup_can_attach() {
  1)               |            cgroup_taskset_first() {
  1)   0.732 us    |              cgroup_taskset_next(); /* = 0xffff93fc8fb20000 */
  1)   1.232 us    |            } /* cgroup_taskset_first = 0xffff93fc8fb20000 */
  1)   0.380 us    |            sched_rt_can_attach(); /* = 0x0 */
  1)   2.335 us    |          } /* cpu_cgroup_can_attach = 0xffffffea */
  1)   4.369 us    |        } /* cgroup_migrate_execute = 0xffffffea */
  1)   7.143 us    |      } /* cgroup_migrate = 0xffffffea */
”h]”(jh  )”}”(hŒn- smart: echo nofuncgraph-retval-hex > trace_options
- hexadecimal: echo funcgraph-retval-hex > trace_options
”h]”j  )”}”(hhh]”(j”  )”}”(hŒ2smart: echo nofuncgraph-retval-hex > trace_options”h]”hÌ)”}”(hj0  h]”hŒ2smart: echo nofuncgraph-retval-hex > trace_options”…””}”(hj 0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M.hj0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj0  ubj”  )”}”(hŒ7hexadecimal: echo funcgraph-retval-hex > trace_options
”h]”hÌ)”}”(hŒ6hexadecimal: echo funcgraph-retval-hex > trace_options”h]”hŒ6hexadecimal: echo funcgraph-retval-hex > trace_options”…””}”(hj70  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M/hj30  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj0  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´M.hj0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M.hj0  ubhÌ)”}”(hŒ#Example with funcgraph-retval-hex::”h]”hŒ"Example with funcgraph-retval-hex:”…””}”(hjW0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M1hj0  ubj´  )”}”(hXÈ  1)               |      cgroup_migrate() {
1)   0.651 us    |        cgroup_migrate_add_task(); /* = 0xffff93fcfd346c00 */
1)               |        cgroup_migrate_execute() {
1)               |          cpu_cgroup_can_attach() {
1)               |            cgroup_taskset_first() {
1)   0.732 us    |              cgroup_taskset_next(); /* = 0xffff93fc8fb20000 */
1)   1.232 us    |            } /* cgroup_taskset_first = 0xffff93fc8fb20000 */
1)   0.380 us    |            sched_rt_can_attach(); /* = 0x0 */
1)   2.335 us    |          } /* cpu_cgroup_can_attach = 0xffffffea */
1)   4.369 us    |        } /* cgroup_migrate_execute = 0xffffffea */
1)   7.143 us    |      } /* cgroup_migrate = 0xffffffea */”h]”hXÈ  1)               |      cgroup_migrate() {
1)   0.651 us    |        cgroup_migrate_add_task(); /* = 0xffff93fcfd346c00 */
1)               |        cgroup_migrate_execute() {
1)               |          cpu_cgroup_can_attach() {
1)               |            cgroup_taskset_first() {
1)   0.732 us    |              cgroup_taskset_next(); /* = 0xffff93fc8fb20000 */
1)   1.232 us    |            } /* cgroup_taskset_first = 0xffff93fc8fb20000 */
1)   0.380 us    |            sched_rt_can_attach(); /* = 0x0 */
1)   2.335 us    |          } /* cpu_cgroup_can_attach = 0xffffffea */
1)   4.369 us    |        } /* cgroup_migrate_execute = 0xffffffea */
1)   7.143 us    |      } /* cgroup_migrate = 0xffffffea */”…””}”hje0  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M3hj0  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M.hjŒ+  h²hubhÌ)”}”(hŒ†At present, there are some limitations when using the funcgraph-retval
option, and these limitations will be eliminated in the future:”h]”hŒ†At present, there are some limitations when using the funcgraph-retval
option, and these limitations will be eliminated in the future:”…””}”(hjy0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M?hjŒ+  h²hubj  )”}”(hhh]”(j”  )”}”(hŒlEven if the function return type is void, a return value will still
be printed, and you can just ignore it.
”h]”hÌ)”}”(hŒkEven if the function return type is void, a return value will still
be printed, and you can just ignore it.”h]”hŒkEven if the function return type is void, a return value will still
be printed, and you can just ignore it.”…””}”(hjŽ0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MBhjŠ0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj‡0  h²hh³hÊh´Nubj”  )”}”(hXn  Even if return values are stored in multiple registers, only the
value contained in the first register will be recorded and printed.
To illustrate, in the x86 architecture, eax and edx are used to store
a 64-bit return value, with the lower 32 bits saved in eax and the
upper 32 bits saved in edx. However, only the value stored in eax
will be recorded and printed.
”h]”hÌ)”}”(hXm  Even if return values are stored in multiple registers, only the
value contained in the first register will be recorded and printed.
To illustrate, in the x86 architecture, eax and edx are used to store
a 64-bit return value, with the lower 32 bits saved in eax and the
upper 32 bits saved in edx. However, only the value stored in eax
will be recorded and printed.”h]”hXm  Even if return values are stored in multiple registers, only the
value contained in the first register will be recorded and printed.
To illustrate, in the x86 architecture, eax and edx are used to store
a 64-bit return value, with the lower 32 bits saved in eax and the
upper 32 bits saved in edx. However, only the value stored in eax
will be recorded and printed.”…””}”(hj¦0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MEhj¢0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj‡0  h²hh³hÊh´Nubj”  )”}”(hX  In certain procedure call standards, such as arm64's AAPCS64, when a
type is smaller than a GPR, it is the responsibility of the consumer
to perform the narrowing, and the upper bits may contain UNKNOWN values.
Therefore, it is advisable to check the code for such cases. For instance,
when using a u8 in a 64-bit GPR, bits [63:8] may contain arbitrary values,
especially when larger types are truncated, whether explicitly or implicitly.
Here are some specific cases to illustrate this point:

**Case One**:

The function narrow_to_u8 is defined as follows::

      u8 narrow_to_u8(u64 val)
      {
              // implicitly truncated
              return val;
      }

It may be compiled to::

      narrow_to_u8:
              < ... ftrace instrumentation ... >
              RET

If you pass 0x123456789abcdef to this function and want to narrow it,
it may be recorded as 0x123456789abcdef instead of 0xef.

**Case Two**:

The function error_if_not_4g_aligned is defined as follows::

      int error_if_not_4g_aligned(u64 val)
      {
              if (val & GENMASK(31, 0))
                      return -EINVAL;

              return 0;
      }

It could be compiled to::

      error_if_not_4g_aligned:
              CBNZ    w0, .Lnot_aligned
              RET                     // bits [31:0] are zero, bits
                                      // [63:32] are UNKNOWN
      .Lnot_aligned:
              MOV    x0, #-EINVAL
              RET

When passing 0x2_0000_0000 to it, the return value may be recorded as
0x2_0000_0000 instead of 0.
”h]”(hÌ)”}”(hXí  In certain procedure call standards, such as arm64's AAPCS64, when a
type is smaller than a GPR, it is the responsibility of the consumer
to perform the narrowing, and the upper bits may contain UNKNOWN values.
Therefore, it is advisable to check the code for such cases. For instance,
when using a u8 in a 64-bit GPR, bits [63:8] may contain arbitrary values,
especially when larger types are truncated, whether explicitly or implicitly.
Here are some specific cases to illustrate this point:”h]”hXï  In certain procedure call standards, such as arm64â€™s AAPCS64, when a
type is smaller than a GPR, it is the responsibility of the consumer
to perform the narrowing, and the upper bits may contain UNKNOWN values.
Therefore, it is advisable to check the code for such cases. For instance,
when using a u8 in a 64-bit GPR, bits [63:8] may contain arbitrary values,
especially when larger types are truncated, whether explicitly or implicitly.
Here are some specific cases to illustrate this point:”…””}”(hj¾0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MLhjº0  ubhÌ)”}”(hŒ**Case One**:”h]”(hŒstrong”“”)”}”(hŒ**Case One**”h]”hŒCase One”…””}”(hjÒ0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÐ0  hjÌ0  ubhŒ:”…””}”(hjÌ0  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MThjº0  ubhÌ)”}”(hŒ1The function narrow_to_u8 is defined as follows::”h]”hŒ0The function narrow_to_u8 is defined as follows:”…””}”(hjê0  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MVhjº0  ubj´  )”}”(hŒPu8 narrow_to_u8(u64 val)
{
        // implicitly truncated
        return val;
}”h]”hŒPu8 narrow_to_u8(u64 val)
{
        // implicitly truncated
        return val;
}”…””}”hjø0  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MXhjº0  ubhÌ)”}”(hŒIt may be compiled to::”h]”hŒIt may be compiled to:”…””}”(hj1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M^hjº0  ubj´  )”}”(hŒDnarrow_to_u8:
        < ... ftrace instrumentation ... >
        RET”h]”hŒDnarrow_to_u8:
        < ... ftrace instrumentation ... >
        RET”…””}”hj1  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M`hjº0  ubhÌ)”}”(hŒ~If you pass 0x123456789abcdef to this function and want to narrow it,
it may be recorded as 0x123456789abcdef instead of 0xef.”h]”hŒ~If you pass 0x123456789abcdef to this function and want to narrow it,
it may be recorded as 0x123456789abcdef instead of 0xef.”…””}”(hj"1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mdhjº0  ubhÌ)”}”(hŒ**Case Two**:”h]”(jÑ0  )”}”(hŒ**Case Two**”h]”hŒCase Two”…””}”(hj41  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÐ0  hj01  ubhŒ:”…””}”(hj01  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mghjº0  ubhÌ)”}”(hŒ<The function error_if_not_4g_aligned is defined as follows::”h]”hŒ;The function error_if_not_4g_aligned is defined as follows:”…””}”(hjL1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mihjº0  ubj´  )”}”(hŒ}int error_if_not_4g_aligned(u64 val)
{
        if (val & GENMASK(31, 0))
                return -EINVAL;

        return 0;
}”h]”hŒ}int error_if_not_4g_aligned(u64 val)
{
        if (val & GENMASK(31, 0))
                return -EINVAL;

        return 0;
}”…””}”hjZ1  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mkhjº0  ubhÌ)”}”(hŒIt could be compiled to::”h]”hŒIt could be compiled to:”…””}”(hjh1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mshjº0  ubj´  )”}”(hŒæerror_if_not_4g_aligned:
        CBNZ    w0, .Lnot_aligned
        RET                     // bits [31:0] are zero, bits
                                // [63:32] are UNKNOWN
.Lnot_aligned:
        MOV    x0, #-EINVAL
        RET”h]”hŒæerror_if_not_4g_aligned:
        CBNZ    w0, .Lnot_aligned
        RET                     // bits [31:0] are zero, bits
                                // [63:32] are UNKNOWN
.Lnot_aligned:
        MOV    x0, #-EINVAL
        RET”…””}”hjv1  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Muhjº0  ubhÌ)”}”(hŒaWhen passing 0x2_0000_0000 to it, the return value may be recorded as
0x2_0000_0000 instead of 0.”h]”hŒaWhen passing 0x2_0000_0000 to it, the return value may be recorded as
0x2_0000_0000 instead of 0.”…””}”(hj„1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M}hjº0  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj‡0  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´MBhjŒ+  h²hubhÌ)”}”(hŒñYou can put some comments on specific functions by using
trace_printk() For example, if you want to put a comment inside
the __might_sleep() function, you just have to include
<linux/ftrace.h> and call trace_printk() inside __might_sleep()::”h]”hŒðYou can put some comments on specific functions by using
trace_printk() For example, if you want to put a comment inside
the __might_sleep() function, you just have to include
<linux/ftrace.h> and call trace_printk() inside __might_sleep():”…””}”(hjž1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M€hjŒ+  h²hubj´  )”}”(hŒ trace_printk("I'm a comment!\n")”h]”hŒ trace_printk("I'm a comment!\n")”…””}”hj¬1  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M…hjŒ+  h²hubhÌ)”}”(hŒwill produce::”h]”hŒwill produce:”…””}”(hjº1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‡hjŒ+  h²hubj´  )”}”(hŒˆ1)               |             __might_sleep() {
1)               |                /* I'm a comment! */
1)   1.449 us    |             }”h]”hŒˆ1)               |             __might_sleep() {
1)               |                /* I'm a comment! */
1)   1.449 us    |             }”…””}”hjÈ1  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M‰hjŒ+  h²hubhÌ)”}”(hŒYou might find other useful features for this tracer in the
following "dynamic ftrace" section such as tracing only specific
functions or tasks.”h]”hŒ”You might find other useful features for this tracer in the
following â€œdynamic ftraceâ€ section such as tracing only specific
functions or tasks.”…””}”(hjÖ1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŽhjŒ+  h²hubeh}”(h]”Œfunction-graph-tracer”ah ]”h"]”Œfunction graph tracer”ah$]”h&]”uh1hµhh·h²hh³hÊh´M<
ubh¶)”}”(hhh]”(h»)”}”(hŒdynamic ftrace”h]”hŒdynamic ftrace”…””}”(hjï1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjì1  h²hh³hÊh´M“ubhÌ)”}”(hXi  If CONFIG_DYNAMIC_FTRACE is set, the system will run with
virtually no overhead when function tracing is disabled. The way
this works is the mcount function call (placed at the start of
every kernel function, produced by the -pg switch in gcc),
starts of pointing to a simple return. (Enabling FTRACE will
include the -pg switch in the compiling of the kernel.)”h]”hXi  If CONFIG_DYNAMIC_FTRACE is set, the system will run with
virtually no overhead when function tracing is disabled. The way
this works is the mcount function call (placed at the start of
every kernel function, produced by the -pg switch in gcc),
starts of pointing to a simple return. (Enabling FTRACE will
include the -pg switch in the compiling of the kernel.)”…””}”(hjý1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M•hjì1  h²hubhÌ)”}”(hX’  At compile time every C file object is run through the
recordmcount program (located in the scripts directory). This
program will parse the ELF headers in the C object to find all
the locations in the .text section that call mcount. Starting
with gcc version 4.6, the -mfentry has been added for x86, which
calls "__fentry__" instead of "mcount". Which is called before
the creation of the stack frame.”h]”hXš  At compile time every C file object is run through the
recordmcount program (located in the scripts directory). This
program will parse the ELF headers in the C object to find all
the locations in the .text section that call mcount. Starting
with gcc version 4.6, the -mfentry has been added for x86, which
calls â€œ__fentry__â€ instead of â€œmcountâ€. Which is called before
the creation of the stack frame.”…””}”(hj2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mœhjì1  h²hubhÌ)”}”(hŒÞNote, not all sections are traced. They may be prevented by either
a notrace, or blocked another way and all inline functions are not
traced. Check the "available_filter_functions" file to see what functions
can be traced.”h]”hŒâNote, not all sections are traced. They may be prevented by either
a notrace, or blocked another way and all inline functions are not
traced. Check the â€œavailable_filter_functionsâ€ file to see what functions
can be traced.”…””}”(hj2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¤hjì1  h²hubhÌ)”}”(hX!  A section called "__mcount_loc" is created that holds
references to all the mcount/fentry call sites in the .text section.
The recordmcount program re-links this section back into the
original object. The final linking stage of the kernel will add all these
references into a single table.”h]”hX%  A section called â€œ__mcount_locâ€ is created that holds
references to all the mcount/fentry call sites in the .text section.
The recordmcount program re-links this section back into the
original object. The final linking stage of the kernel will add all these
references into a single table.”…””}”(hj'2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M©hjì1  h²hubhÌ)”}”(hXÔ  On boot up, before SMP is initialized, the dynamic ftrace code
scans this table and updates all the locations into nops. It
also records the locations, which are added to the
available_filter_functions list.  Modules are processed as they
are loaded and before they are executed.  When a module is
unloaded, it also removes its functions from the ftrace function
list. This is automatic in the module unload code, and the
module author does not need to worry about it.”h]”hXÔ  On boot up, before SMP is initialized, the dynamic ftrace code
scans this table and updates all the locations into nops. It
also records the locations, which are added to the
available_filter_functions list.  Modules are processed as they
are loaded and before they are executed.  When a module is
unloaded, it also removes its functions from the ftrace function
list. This is automatic in the module unload code, and the
module author does not need to worry about it.”…””}”(hj52  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¯hjì1  h²hubhÌ)”}”(hXâ  When tracing is enabled, the process of modifying the function
tracepoints is dependent on architecture. The old method is to use
kstop_machine to prevent races with the CPUs executing code being
modified (which can cause the CPU to do undesirable things, especially
if the modified code crosses cache (or page) boundaries), and the nops are
patched back to calls. But this time, they do not call mcount
(which is just a function stub). They now call into the ftrace
infrastructure.”h]”hXâ  When tracing is enabled, the process of modifying the function
tracepoints is dependent on architecture. The old method is to use
kstop_machine to prevent races with the CPUs executing code being
modified (which can cause the CPU to do undesirable things, especially
if the modified code crosses cache (or page) boundaries), and the nops are
patched back to calls. But this time, they do not call mcount
(which is just a function stub). They now call into the ftrace
infrastructure.”…””}”(hjC2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¸hjì1  h²hubhÌ)”}”(hX%  The new method of modifying the function tracepoints is to place
a breakpoint at the location to be modified, sync all CPUs, modify
the rest of the instruction not covered by the breakpoint. Sync
all CPUs again, and then remove the breakpoint with the finished
version to the ftrace call site.”h]”hX%  The new method of modifying the function tracepoints is to place
a breakpoint at the location to be modified, sync all CPUs, modify
the rest of the instruction not covered by the breakpoint. Sync
all CPUs again, and then remove the breakpoint with the finished
version to the ftrace call site.”…””}”(hjQ2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÁhjì1  h²hubhÌ)”}”(hŒ»Some archs do not even need to monkey around with the synchronization,
and can just slap the new code on top of the old without any
problems with other CPUs executing it at the same time.”h]”hŒ»Some archs do not even need to monkey around with the synchronization,
and can just slap the new code on top of the old without any
problems with other CPUs executing it at the same time.”…””}”(hj_2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÇhjì1  h²hubhÌ)”}”(hŒÈOne special side-effect to the recording of the functions being
traced is that we can now selectively choose which functions we
wish to trace and which ones we want the mcount calls to remain
as nops.”h]”hŒÈOne special side-effect to the recording of the functions being
traced is that we can now selectively choose which functions we
wish to trace and which ones we want the mcount calls to remain
as nops.”…””}”(hjm2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MËhjì1  h²hubhÌ)”}”(hŒhTwo files are used, one for enabling and one for disabling the
tracing of specified functions. They are:”h]”hŒhTwo files are used, one for enabling and one for disabling the
tracing of specified functions. They are:”…””}”(hj{2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÐhjì1  h²hubjh  )”}”(hŒset_ftrace_filter
”h]”hÌ)”}”(hŒset_ftrace_filter”h]”hŒset_ftrace_filter”…””}”(hj2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÓhj‰2  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÓhjì1  h²hubhÌ)”}”(hŒand”h]”hŒand”…””}”(hj¡2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÕhjì1  h²hubjh  )”}”(hŒset_ftrace_notrace
”h]”hÌ)”}”(hŒset_ftrace_notrace”h]”hŒset_ftrace_notrace”…””}”(hj³2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M×hj¯2  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´M×hjì1  h²hubhÌ)”}”(hŒKA list of available functions that you can add to these files is
listed in:”h]”hŒKA list of available functions that you can add to these files is
listed in:”…””}”(hjÇ2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÙhjì1  h²hubjh  )”}”(hŒavailable_filter_functions
”h]”hÌ)”}”(hŒavailable_filter_functions”h]”hŒavailable_filter_functions”…””}”(hjÙ2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÜhjÕ2  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´MÜhjì1  h²hubj´  )”}”(hŒ‹# cat available_filter_functions
put_prev_task_idle
kmem_cache_create
pick_next_task_rt
cpus_read_lock
pick_next_task_fair
mutex_lock
[...]”h]”hŒ‹# cat available_filter_functions
put_prev_task_idle
kmem_cache_create
pick_next_task_rt
cpus_read_lock
pick_next_task_fair
mutex_lock
[...]”…””}”hjí2  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Màhjì1  h²hubhÌ)”}”(hŒ@If I am only interested in sys_nanosleep and hrtimer_interrupt::”h]”hŒ?If I am only interested in sys_nanosleep and hrtimer_interrupt:”…””}”(hjû2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Méhjì1  h²hubj´  )”}”(hX  # echo sys_nanosleep hrtimer_interrupt > set_ftrace_filter
# echo function > current_tracer
# echo 1 > tracing_on
# usleep 1
# echo 0 > tracing_on
# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 5/5   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          usleep-2665  [001] ....  4186.475355: sys_nanosleep <-system_call_fastpath
          <idle>-0     [001] d.h1  4186.475409: hrtimer_interrupt <-smp_apic_timer_interrupt
          usleep-2665  [001] d.h1  4186.475426: hrtimer_interrupt <-smp_apic_timer_interrupt
          <idle>-0     [003] d.h1  4186.475426: hrtimer_interrupt <-smp_apic_timer_interrupt
          <idle>-0     [002] d.h1  4186.475427: hrtimer_interrupt <-smp_apic_timer_interrupt”h]”hX  # echo sys_nanosleep hrtimer_interrupt > set_ftrace_filter
# echo function > current_tracer
# echo 1 > tracing_on
# usleep 1
# echo 0 > tracing_on
# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 5/5   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          usleep-2665  [001] ....  4186.475355: sys_nanosleep <-system_call_fastpath
          <idle>-0     [001] d.h1  4186.475409: hrtimer_interrupt <-smp_apic_timer_interrupt
          usleep-2665  [001] d.h1  4186.475426: hrtimer_interrupt <-smp_apic_timer_interrupt
          <idle>-0     [003] d.h1  4186.475426: hrtimer_interrupt <-smp_apic_timer_interrupt
          <idle>-0     [002] d.h1  4186.475427: hrtimer_interrupt <-smp_apic_timer_interrupt”…””}”hj	3  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mëhjì1  h²hubhÌ)”}”(hŒATo see which functions are being traced, you can cat the file:
::”h]”hŒ>To see which functions are being traced, you can cat the file:”…””}”(hj3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjì1  h²hubj´  )”}”(hŒ7# cat set_ftrace_filter
hrtimer_interrupt
sys_nanosleep”h]”hŒ7# cat set_ftrace_filter
hrtimer_interrupt
sys_nanosleep”…””}”hj%3  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhjì1  h²hubhÌ)”}”(hŒDPerhaps this is not enough. The filters also allow glob(7) matching.”h]”hŒDPerhaps this is not enough. The filters also allow glob(7) matching.”…””}”(hj33  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M
hjì1  h²hubjh  )”}”(hX  ``<match>*``
      will match functions that begin with <match>
``*<match>``
      will match functions that end with <match>
``*<match>*``
      will match functions that have <match> in it
``<match1>*<match2>``
      will match functions that begin with <match1> and end with <match2>
”h]”jŽ  )”}”(hhh]”(j“  )”}”(hŒ9``<match>*``
will match functions that begin with <match>”h]”(j™  )”}”(hŒ``<match>*``”h]”hŒliteral”“”)”}”(hjN3  h]”hŒ<match>*”…””}”(hjR3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jP3  hjL3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´MhjH3  ubj©  )”}”(hhh]”hÌ)”}”(hŒ,will match functions that begin with <match>”h]”hŒ,will match functions that begin with <match>”…””}”(hjh3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhje3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjH3  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MhjE3  ubj“  )”}”(hŒ7``*<match>``
will match functions that end with <match>”h]”(j™  )”}”(hŒ``*<match>``”h]”jQ3  )”}”(hjˆ3  h]”hŒ*<match>”…””}”(hjŠ3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jP3  hj†3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhj‚3  ubj©  )”}”(hhh]”hÌ)”}”(hŒ*will match functions that end with <match>”h]”hŒ*will match functions that end with <match>”…””}”(hj 3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hj‚3  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MhjE3  ubj“  )”}”(hŒ:``*<match>*``
will match functions that have <match> in it”h]”(j™  )”}”(hŒ``*<match>*``”h]”jQ3  )”}”(hjÀ3  h]”hŒ	*<match>*”…””}”(hjÂ3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jP3  hj¾3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhjº3  ubj©  )”}”(hhh]”hÌ)”}”(hŒ,will match functions that have <match> in it”h]”hŒ,will match functions that have <match> in it”…””}”(hjØ3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjÕ3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjº3  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MhjE3  ubj“  )”}”(hŒZ``<match1>*<match2>``
will match functions that begin with <match1> and end with <match2>
”h]”(j™  )”}”(hŒ``<match1>*<match2>``”h]”jQ3  )”}”(hjø3  h]”hŒ<match1>*<match2>”…””}”(hjú3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jP3  hjö3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j˜  h³hÊh´Mhjò3  ubj©  )”}”(hhh]”hÌ)”}”(hŒCwill match functions that begin with <match1> and end with <match2>”h]”hŒCwill match functions that begin with <match1> and end with <match2>”…””}”(hj4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj4  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨  hjò3  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j’  h³hÊh´MhjE3  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjA3  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhjì1  h²hubhŒnote”“”)”}”(hŒIt is better to use quotes to enclose the wild cards,
otherwise the shell may expand the parameters into names
of files in the local directory.”h]”hÌ)”}”(hŒIt is better to use quotes to enclose the wild cards,
otherwise the shell may expand the parameters into names
of files in the local directory.”h]”hŒIt is better to use quotes to enclose the wild cards,
otherwise the shell may expand the parameters into names
of files in the local directory.”…””}”(hj<4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj84  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j64  hjì1  h²hh³hÊh´Nubj´  )”}”(hŒ&# echo 'hrtimer_*' > set_ftrace_filter”h]”hŒ&# echo 'hrtimer_*' > set_ftrace_filter”…””}”hjP4  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhjì1  h²hubhÌ)”}”(hŒ
Produces::”h]”hŒ	Produces:”…””}”(hj^4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjì1  h²hubj´  )”}”(hXŠ  # tracer: function
#
# entries-in-buffer/entries-written: 897/897   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          <idle>-0     [003] dN.1  4228.547803: hrtimer_cancel <-tick_nohz_idle_exit
          <idle>-0     [003] dN.1  4228.547804: hrtimer_try_to_cancel <-hrtimer_cancel
          <idle>-0     [003] dN.2  4228.547805: hrtimer_force_reprogram <-__remove_hrtimer
          <idle>-0     [003] dN.1  4228.547805: hrtimer_forward <-tick_nohz_idle_exit
          <idle>-0     [003] dN.1  4228.547805: hrtimer_start_range_ns <-hrtimer_start_expires.constprop.11
          <idle>-0     [003] d..1  4228.547858: hrtimer_get_next_event <-get_next_timer_interrupt
          <idle>-0     [003] d..1  4228.547859: hrtimer_start <-__tick_nohz_idle_enter
          <idle>-0     [003] d..2  4228.547860: hrtimer_force_reprogram <-__rem”h]”hXŠ  # tracer: function
#
# entries-in-buffer/entries-written: 897/897   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          <idle>-0     [003] dN.1  4228.547803: hrtimer_cancel <-tick_nohz_idle_exit
          <idle>-0     [003] dN.1  4228.547804: hrtimer_try_to_cancel <-hrtimer_cancel
          <idle>-0     [003] dN.2  4228.547805: hrtimer_force_reprogram <-__remove_hrtimer
          <idle>-0     [003] dN.1  4228.547805: hrtimer_forward <-tick_nohz_idle_exit
          <idle>-0     [003] dN.1  4228.547805: hrtimer_start_range_ns <-hrtimer_start_expires.constprop.11
          <idle>-0     [003] d..1  4228.547858: hrtimer_get_next_event <-get_next_timer_interrupt
          <idle>-0     [003] d..1  4228.547859: hrtimer_start <-__tick_nohz_idle_enter
          <idle>-0     [003] d..2  4228.547860: hrtimer_force_reprogram <-__rem”…””}”hjl4  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M hjì1  h²hubhÌ)”}”(hŒ)Notice that we lost the sys_nanosleep.
::”h]”hŒ&Notice that we lost the sys_nanosleep.”…””}”(hjz4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M4hjì1  h²hubj´  )”}”(hX>  # cat set_ftrace_filter
hrtimer_run_queues
hrtimer_run_pending
hrtimer_setup
hrtimer_cancel
hrtimer_try_to_cancel
hrtimer_forward
hrtimer_start
hrtimer_reprogram
hrtimer_force_reprogram
hrtimer_get_next_event
hrtimer_interrupt
hrtimer_nanosleep
hrtimer_wakeup
hrtimer_get_remaining
hrtimer_get_res
hrtimer_init_sleeper”h]”hX>  # cat set_ftrace_filter
hrtimer_run_queues
hrtimer_run_pending
hrtimer_setup
hrtimer_cancel
hrtimer_try_to_cancel
hrtimer_forward
hrtimer_start
hrtimer_reprogram
hrtimer_force_reprogram
hrtimer_get_next_event
hrtimer_interrupt
hrtimer_nanosleep
hrtimer_wakeup
hrtimer_get_remaining
hrtimer_get_res
hrtimer_init_sleeper”…””}”hjˆ4  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M7hjì1  h²hubhÌ)”}”(hŒ‚This is because the '>' and '>>' act just like they do in bash.
To rewrite the filters, use '>'
To append to the filters, use '>>'”h]”hŒ’This is because the â€˜>â€™ and â€˜>>â€™ act just like they do in bash.
To rewrite the filters, use â€˜>â€™
To append to the filters, use â€˜>>â€™”…””}”(hj–4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MJhjì1  h²hubhÌ)”}”(hŒDTo clear out a filter so that all functions will be recorded
again::”h]”hŒCTo clear out a filter so that all functions will be recorded
again:”…””}”(hj¤4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MNhjì1  h²hubj´  )”}”(hŒ4# echo > set_ftrace_filter
# cat set_ftrace_filter
#”h]”hŒ4# echo > set_ftrace_filter
# cat set_ftrace_filter
#”…””}”hj²4  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MQhjì1  h²hubhÌ)”}”(hŒAgain, now we want to append.”h]”hŒAgain, now we want to append.”…””}”(hjÀ4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MUhjì1  h²hubj´  )”}”(hXÃ  # echo sys_nanosleep > set_ftrace_filter
# cat set_ftrace_filter
sys_nanosleep
# echo 'hrtimer_*' >> set_ftrace_filter
# cat set_ftrace_filter
hrtimer_run_queues
hrtimer_run_pending
hrtimer_setup
hrtimer_cancel
hrtimer_try_to_cancel
hrtimer_forward
hrtimer_start
hrtimer_reprogram
hrtimer_force_reprogram
hrtimer_get_next_event
hrtimer_interrupt
sys_nanosleep
hrtimer_nanosleep
hrtimer_wakeup
hrtimer_get_remaining
hrtimer_get_res
hrtimer_init_sleeper”h]”hXÃ  # echo sys_nanosleep > set_ftrace_filter
# cat set_ftrace_filter
sys_nanosleep
# echo 'hrtimer_*' >> set_ftrace_filter
# cat set_ftrace_filter
hrtimer_run_queues
hrtimer_run_pending
hrtimer_setup
hrtimer_cancel
hrtimer_try_to_cancel
hrtimer_forward
hrtimer_start
hrtimer_reprogram
hrtimer_force_reprogram
hrtimer_get_next_event
hrtimer_interrupt
sys_nanosleep
hrtimer_nanosleep
hrtimer_wakeup
hrtimer_get_remaining
hrtimer_get_res
hrtimer_init_sleeper”…””}”hjÎ4  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MYhjì1  h²hubhÌ)”}”(hŒEThe set_ftrace_notrace prevents those functions from being
traced.
::”h]”hŒBThe set_ftrace_notrace prevents those functions from being
traced.”…””}”(hjÜ4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mqhjì1  h²hubj´  )”}”(hŒ0# echo '*preempt*' '*lock*' > set_ftrace_notrace”h]”hŒ0# echo '*preempt*' '*lock*' > set_ftrace_notrace”…””}”hjê4  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Muhjì1  h²hubhÌ)”}”(hŒ
Produces::”h]”hŒ	Produces:”…””}”(hjø4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mwhjì1  h²hubj´  )”}”(hX†  # tracer: function
#
# entries-in-buffer/entries-written: 39608/39608   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1994  [000] ....  4342.324896: file_ra_state_init <-do_dentry_open
            bash-1994  [000] ....  4342.324897: open_check_o_direct <-do_last
            bash-1994  [000] ....  4342.324897: ima_file_check <-do_last
            bash-1994  [000] ....  4342.324898: process_measurement <-ima_file_check
            bash-1994  [000] ....  4342.324898: ima_get_action <-process_measurement
            bash-1994  [000] ....  4342.324898: ima_match_policy <-ima_get_action
            bash-1994  [000] ....  4342.324899: do_truncate <-do_last
            bash-1994  [000] ....  4342.324899: setattr_should_drop_suidgid <-do_truncate
            bash-1994  [000] ....  4342.324899: notify_change <-do_truncate
            bash-1994  [000] ....  4342.324900: current_fs_time <-notify_change
            bash-1994  [000] ....  4342.324900: current_kernel_time <-current_fs_time
            bash-1994  [000] ....  4342.324900: timespec_trunc <-current_fs_time”h]”hX†  # tracer: function
#
# entries-in-buffer/entries-written: 39608/39608   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1994  [000] ....  4342.324896: file_ra_state_init <-do_dentry_open
            bash-1994  [000] ....  4342.324897: open_check_o_direct <-do_last
            bash-1994  [000] ....  4342.324897: ima_file_check <-do_last
            bash-1994  [000] ....  4342.324898: process_measurement <-ima_file_check
            bash-1994  [000] ....  4342.324898: ima_get_action <-process_measurement
            bash-1994  [000] ....  4342.324898: ima_match_policy <-ima_get_action
            bash-1994  [000] ....  4342.324899: do_truncate <-do_last
            bash-1994  [000] ....  4342.324899: setattr_should_drop_suidgid <-do_truncate
            bash-1994  [000] ....  4342.324899: notify_change <-do_truncate
            bash-1994  [000] ....  4342.324900: current_fs_time <-notify_change
            bash-1994  [000] ....  4342.324900: current_kernel_time <-current_fs_time
            bash-1994  [000] ....  4342.324900: timespec_trunc <-current_fs_time”…””•ç     }”hj5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Myhjì1  h²hubhÌ)”}”(hŒ8We can see that there's no more lock or preempt tracing.”h]”hŒ:We can see that thereâ€™s no more lock or preempt tracing.”…””}”(hj5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‘hjì1  h²hubeh}”(h]”Œdynamic-ftrace”ah ]”h"]”Œdynamic ftrace”ah$]”h&]”uh1hµhh·h²hh³hÊh´M“ubh¶)”}”(hhh]”(h»)”}”(hŒ$Selecting function filters via index”h]”hŒ$Selecting function filters via index”…””}”(hj-5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj*5  h²hh³hÊh´M”ubhÌ)”}”(hXô  Because processing of strings is expensive (the address of the function
needs to be looked up before comparing to the string being passed in),
an index can be used as well to enable functions. This is useful in the
case of setting thousands of specific functions at a time. By passing
in a list of numbers, no string processing will occur. Instead, the function
at the specific location in the internal array (which corresponds to the
functions in the "available_filter_functions" file), is selected.”h]”hXø  Because processing of strings is expensive (the address of the function
needs to be looked up before comparing to the string being passed in),
an index can be used as well to enable functions. This is useful in the
case of setting thousands of specific functions at a time. By passing
in a list of numbers, no string processing will occur. Instead, the function
at the specific location in the internal array (which corresponds to the
functions in the â€œavailable_filter_functionsâ€ file), is selected.”…””}”(hj;5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M–hj*5  h²hubj´  )”}”(hŒ# echo 1 > set_ftrace_filter”h]”hŒ# echo 1 > set_ftrace_filter”…””}”hjI5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M hj*5  h²hubhÌ)”}”(hŒEWill select the first function listed in "available_filter_functions"”h]”hŒIWill select the first function listed in â€œavailable_filter_functionsâ€”…””}”(hjW5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¢hj*5  h²hubj´  )”}”(hX  # head -1 available_filter_functions
trace_initcall_finish_cb

# cat set_ftrace_filter
trace_initcall_finish_cb

# head -50 available_filter_functions | tail -1
x86_pmu_commit_txn

# echo 1 50 > set_ftrace_filter
# cat set_ftrace_filter
trace_initcall_finish_cb
x86_pmu_commit_txn”h]”hX  # head -1 available_filter_functions
trace_initcall_finish_cb

# cat set_ftrace_filter
trace_initcall_finish_cb

# head -50 available_filter_functions | tail -1
x86_pmu_commit_txn

# echo 1 50 > set_ftrace_filter
# cat set_ftrace_filter
trace_initcall_finish_cb
x86_pmu_commit_txn”…””}”hje5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¦hj*5  h²hubeh}”(h]”Œ$selecting-function-filters-via-index”ah ]”h"]”Œ$selecting function filters via index”ah$]”h&]”uh1hµhh·h²hh³hÊh´M”ubh¶)”}”(hhh]”(h»)”}”(hŒ-Dynamic ftrace with the function graph tracer”h]”hŒ-Dynamic ftrace with the function graph tracer”…””}”(hj~5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj{5  h²hh³hÊh´MµubhÌ)”}”(hŒ´Although what has been explained above concerns both the
function tracer and the function-graph-tracer, there are some
special features only available in the function-graph tracer.”h]”hŒ´Although what has been explained above concerns both the
function tracer and the function-graph-tracer, there are some
special features only available in the function-graph tracer.”…””}”(hjŒ5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M·hj{5  h²hubhÌ)”}”(hŒxIf you want to trace only one function and all of its children,
you just have to echo its name into set_graph_function::”h]”hŒwIf you want to trace only one function and all of its children,
you just have to echo its name into set_graph_function:”…””}”(hjš5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M»hj{5  h²hubj´  )”}”(hŒ$echo __do_fault > set_graph_function”h]”hŒ$echo __do_fault > set_graph_function”…””}”hj¨5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¾hj{5  h²hubhÌ)”}”(hŒJwill produce the following "expanded" trace of the __do_fault()
function::”h]”hŒMwill produce the following â€œexpandedâ€ trace of the __do_fault()
function:”…””}”(hj¶5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÀhj{5  h²hubj´  )”}”(hXÅ  0)               |  __do_fault() {
0)               |    filemap_fault() {
0)               |      find_lock_page() {
0)   0.804 us    |        find_get_page();
0)               |        __might_sleep() {
0)   1.329 us    |        }
0)   3.904 us    |      }
0)   4.979 us    |    }
0)   0.653 us    |    _spin_lock();
0)   0.578 us    |    page_add_file_rmap();
0)   0.525 us    |    native_set_pte_at();
0)   0.585 us    |    _spin_unlock();
0)               |    unlock_page() {
0)   0.541 us    |      page_waitqueue();
0)   0.639 us    |      __wake_up_bit();
0)   2.786 us    |    }
0) + 14.237 us   |  }
0)               |  __do_fault() {
0)               |    filemap_fault() {
0)               |      find_lock_page() {
0)   0.698 us    |        find_get_page();
0)               |        __might_sleep() {
0)   1.412 us    |        }
0)   3.950 us    |      }
0)   5.098 us    |    }
0)   0.631 us    |    _spin_lock();
0)   0.571 us    |    page_add_file_rmap();
0)   0.526 us    |    native_set_pte_at();
0)   0.586 us    |    _spin_unlock();
0)               |    unlock_page() {
0)   0.533 us    |      page_waitqueue();
0)   0.638 us    |      __wake_up_bit();
0)   2.793 us    |    }
0) + 14.012 us   |  }”h]”hXÅ  0)               |  __do_fault() {
0)               |    filemap_fault() {
0)               |      find_lock_page() {
0)   0.804 us    |        find_get_page();
0)               |        __might_sleep() {
0)   1.329 us    |        }
0)   3.904 us    |      }
0)   4.979 us    |    }
0)   0.653 us    |    _spin_lock();
0)   0.578 us    |    page_add_file_rmap();
0)   0.525 us    |    native_set_pte_at();
0)   0.585 us    |    _spin_unlock();
0)               |    unlock_page() {
0)   0.541 us    |      page_waitqueue();
0)   0.639 us    |      __wake_up_bit();
0)   2.786 us    |    }
0) + 14.237 us   |  }
0)               |  __do_fault() {
0)               |    filemap_fault() {
0)               |      find_lock_page() {
0)   0.698 us    |        find_get_page();
0)               |        __might_sleep() {
0)   1.412 us    |        }
0)   3.950 us    |      }
0)   5.098 us    |    }
0)   0.631 us    |    _spin_lock();
0)   0.571 us    |    page_add_file_rmap();
0)   0.526 us    |    native_set_pte_at();
0)   0.586 us    |    _spin_unlock();
0)               |    unlock_page() {
0)   0.533 us    |      page_waitqueue();
0)   0.638 us    |      __wake_up_bit();
0)   2.793 us    |    }
0) + 14.012 us   |  }”…””}”hjÄ5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÃhj{5  h²hubhÌ)”}”(hŒ/You can also expand several functions at once::”h]”hŒ.You can also expand several functions at once:”…””}”(hjÒ5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mæhj{5  h²hubj´  )”}”(hŒGecho sys_open > set_graph_function
echo sys_close >> set_graph_function”h]”hŒGecho sys_open > set_graph_function
echo sys_close >> set_graph_function”…””}”hjà5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mèhj{5  h²hubhÌ)”}”(hŒYNow if you want to go back to trace all functions you can clear
this special filter via::”h]”hŒXNow if you want to go back to trace all functions you can clear
this special filter via:”…””}”(hjî5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mëhj{5  h²hubj´  )”}”(hŒecho > set_graph_function”h]”hŒecho > set_graph_function”…””}”hjü5  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mîhj{5  h²hubeh}”(h]”Œ-dynamic-ftrace-with-the-function-graph-tracer”ah ]”h"]”Œ-dynamic ftrace with the function graph tracer”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mµubh¶)”}”(hhh]”(h»)”}”(hŒftrace_enabled”h]”hŒftrace_enabled”…””}”(hj6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj6  h²hh³hÊh´Mòubj74  )”}”(hŒ™Disabling ftrace via this switch is deprecated. Writing 0 is refused
with -EOPNOTSUPP and logs a warning; writing 1 and reading the value
are unaffected.”h]”hÌ)”}”(hŒ™Disabling ftrace via this switch is deprecated. Writing 0 is refused
with -EOPNOTSUPP and logs a warning; writing 1 and reading the value
are unaffected.”h]”hŒ™Disabling ftrace via this switch is deprecated. Writing 0 is refused
with -EOPNOTSUPP and logs a warning; writing 1 and reading the value
are unaffected.”…””}”(hj'6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mõhj#6  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j64  hj6  h²hh³hÊh´NubhÌ)”}”(hX±  Note, the proc sysctl ftrace_enable is a big on/off switch for the
function tracer. By default it is enabled (when function tracing is
enabled in the kernel). If it is disabled, all function tracing is
disabled. This includes not only the function tracers for ftrace, but
also for any other uses (perf, kprobes, stack tracing, profiling, etc). It
cannot be disabled if there is a callback with FTRACE_OPS_FL_PERMANENT set
registered.”h]”hX±  Note, the proc sysctl ftrace_enable is a big on/off switch for the
function tracer. By default it is enabled (when function tracing is
enabled in the kernel). If it is disabled, all function tracing is
disabled. This includes not only the function tracers for ftrace, but
also for any other uses (perf, kprobes, stack tracing, profiling, etc). It
cannot be disabled if there is a callback with FTRACE_OPS_FL_PERMANENT set
registered.”…””}”(hj;6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mùhj6  h²hubhÌ)”}”(hŒPlease disable this with care.”h]”hŒPlease disable this with care.”…””}”(hjI6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj6  h²hubhÌ)”}”(hŒ(This can be disable (and enabled) with::”h]”hŒ'This can be disable (and enabled) with:”…””}”(hjW6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj6  h²hubj´  )”}”(hŒ˜ sysctl kernel.ftrace_enabled=0
 sysctl kernel.ftrace_enabled=1

or

 echo 0 > /proc/sys/kernel/ftrace_enabled
 echo 1 > /proc/sys/kernel/ftrace_enabled”h]”hŒ˜ sysctl kernel.ftrace_enabled=0
 sysctl kernel.ftrace_enabled=1

or

 echo 0 > /proc/sys/kernel/ftrace_enabled
 echo 1 > /proc/sys/kernel/ftrace_enabled”…””}”hje6  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhj6  h²hubeh}”(h]”Œftrace-enabled”ah ]”h"]”Œftrace_enabled”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mòubh¶)”}”(hhh]”(h»)”}”(hŒFilter commands”h]”hŒFilter commands”…””}”(hj~6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj{6  h²hh³hÊh´MubhÌ)”}”(hŒkA few commands are supported by the set_ftrace_filter interface.
Trace commands have the following format::”h]”hŒjA few commands are supported by the set_ftrace_filter interface.
Trace commands have the following format:”…””}”(hjŒ6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{6  h²hubj´  )”}”(hŒ <function>:<command>:<parameter>”h]”hŒ <function>:<command>:<parameter>”…””}”hjš6  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhj{6  h²hubhÌ)”}”(hŒ%The following commands are supported:”h]”hŒ%The following commands are supported:”…””}”(hj¨6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj{6  h²hubj  )”}”(hhh]”(j”  )”}”(hX™  mod:
This command enables function filtering per module. The
parameter defines the module. For example, if only the write*
functions in the ext3 module are desired, run:

 echo 'write*:mod:ext3' > set_ftrace_filter

This command interacts with the filter in the same way as
filtering based on function names. Thus, adding more functions
in a different module is accomplished by appending (>>) to the
filter file. Remove specific module functions by prepending
'!'::

 echo '!writeback*:mod:ext3' >> set_ftrace_filter

Mod command supports module globbing. Disable tracing for all
functions except a specific module::

 echo '!*:mod:!ext3' >> set_ftrace_filter

Disable tracing for all modules, but still trace kernel::

 echo '!*:mod:*' >> set_ftrace_filter

Enable filter only for kernel::

 echo '*write*:mod:!*' >> set_ftrace_filter

Enable filter for module globbing::

 echo '*write*:mod:*snd*' >> set_ftrace_filter
”h]”(hÌ)”}”(hŒ©mod:
This command enables function filtering per module. The
parameter defines the module. For example, if only the write*
functions in the ext3 module are desired, run:”h]”hŒ©mod:
This command enables function filtering per module. The
parameter defines the module. For example, if only the write*
functions in the ext3 module are desired, run:”…””}”(hj½6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj¹6  ubjh  )”}”(hŒ+echo 'write*:mod:ext3' > set_ftrace_filter
”h]”hÌ)”}”(hŒ*echo 'write*:mod:ext3' > set_ftrace_filter”h]”hŒ.echo â€˜write*:mod:ext3â€™ > set_ftrace_filter”…””}”(hjÏ6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjË6  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj¹6  ubhÌ)”}”(hŒùThis command interacts with the filter in the same way as
filtering based on function names. Thus, adding more functions
in a different module is accomplished by appending (>>) to the
filter file. Remove specific module functions by prepending
'!'::”h]”hŒüThis command interacts with the filter in the same way as
filtering based on function names. Thus, adding more functions
in a different module is accomplished by appending (>>) to the
filter file. Remove specific module functions by prepending
â€˜!â€™:”…””}”(hjã6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj¹6  ubj´  )”}”(hŒ0echo '!writeback*:mod:ext3' >> set_ftrace_filter”h]”hŒ0echo '!writeback*:mod:ext3' >> set_ftrace_filter”…””}”hjñ6  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M%hj¹6  ubhÌ)”}”(hŒbMod command supports module globbing. Disable tracing for all
functions except a specific module::”h]”hŒaMod command supports module globbing. Disable tracing for all
functions except a specific module:”…””}”(hjÿ6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M'hj¹6  ubj´  )”}”(hŒ(echo '!*:mod:!ext3' >> set_ftrace_filter”h]”hŒ(echo '!*:mod:!ext3' >> set_ftrace_filter”…””}”hj7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M*hj¹6  ubhÌ)”}”(hŒ9Disable tracing for all modules, but still trace kernel::”h]”hŒ8Disable tracing for all modules, but still trace kernel:”…””}”(hj7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M,hj¹6  ubj´  )”}”(hŒ$echo '!*:mod:*' >> set_ftrace_filter”h]”hŒ$echo '!*:mod:*' >> set_ftrace_filter”…””}”hj)7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M.hj¹6  ubhÌ)”}”(hŒEnable filter only for kernel::”h]”hŒEnable filter only for kernel:”…””}”(hj77  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M0hj¹6  ubj´  )”}”(hŒ*echo '*write*:mod:!*' >> set_ftrace_filter”h]”hŒ*echo '*write*:mod:!*' >> set_ftrace_filter”…””}”hjE7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M2hj¹6  ubhÌ)”}”(hŒ#Enable filter for module globbing::”h]”hŒ"Enable filter for module globbing:”…””}”(hjS7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M4hj¹6  ubj´  )”}”(hŒ-echo '*write*:mod:*snd*' >> set_ftrace_filter”h]”hŒ-echo '*write*:mod:*snd*' >> set_ftrace_filter”…””}”hja7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M6hj¹6  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¶6  h²hh³hÊh´Nubj”  )”}”(hXE  traceon/traceoff:
These commands turn tracing on and off when the specified
functions are hit. The parameter determines how many times the
tracing system is turned on and off. If unspecified, there is
no limit. For example, to disable tracing when a schedule bug
is hit the first 5 times, run::

 echo '__schedule_bug:traceoff:5' > set_ftrace_filter

To always disable tracing when __schedule_bug is hit::

 echo '__schedule_bug:traceoff' > set_ftrace_filter

These commands are cumulative whether or not they are appended
to set_ftrace_filter. To remove a command, prepend it by '!'
and drop the parameter::

 echo '!__schedule_bug:traceoff:0' > set_ftrace_filter

The above removes the traceoff command for __schedule_bug
that have a counter. To remove commands without counters::

 echo '!__schedule_bug:traceoff' > set_ftrace_filter
”h]”(hÌ)”}”(hX&  traceon/traceoff:
These commands turn tracing on and off when the specified
functions are hit. The parameter determines how many times the
tracing system is turned on and off. If unspecified, there is
no limit. For example, to disable tracing when a schedule bug
is hit the first 5 times, run::”h]”hX%  traceon/traceoff:
These commands turn tracing on and off when the specified
functions are hit. The parameter determines how many times the
tracing system is turned on and off. If unspecified, there is
no limit. For example, to disable tracing when a schedule bug
is hit the first 5 times, run:”…””}”(hjy7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M8hju7  ubj´  )”}”(hŒ4echo '__schedule_bug:traceoff:5' > set_ftrace_filter”h]”hŒ4echo '__schedule_bug:traceoff:5' > set_ftrace_filter”…””}”hj‡7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M?hju7  ubhÌ)”}”(hŒ6To always disable tracing when __schedule_bug is hit::”h]”hŒ5To always disable tracing when __schedule_bug is hit:”…””}”(hj•7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MAhju7  ubj´  )”}”(hŒ2echo '__schedule_bug:traceoff' > set_ftrace_filter”h]”hŒ2echo '__schedule_bug:traceoff' > set_ftrace_filter”…””}”hj£7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MChju7  ubhÌ)”}”(hŒ”These commands are cumulative whether or not they are appended
to set_ftrace_filter. To remove a command, prepend it by '!'
and drop the parameter::”h]”hŒ—These commands are cumulative whether or not they are appended
to set_ftrace_filter. To remove a command, prepend it by â€˜!â€™
and drop the parameter:”…””}”(hj±7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MEhju7  ubj´  )”}”(hŒ5echo '!__schedule_bug:traceoff:0' > set_ftrace_filter”h]”hŒ5echo '!__schedule_bug:traceoff:0' > set_ftrace_filter”…””}”hj¿7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MIhju7  ubhÌ)”}”(hŒtThe above removes the traceoff command for __schedule_bug
that have a counter. To remove commands without counters::”h]”hŒsThe above removes the traceoff command for __schedule_bug
that have a counter. To remove commands without counters:”…””}”(hjÍ7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MKhju7  ubj´  )”}”(hŒ3echo '!__schedule_bug:traceoff' > set_ftrace_filter”h]”hŒ3echo '!__schedule_bug:traceoff' > set_ftrace_filter”…””}”hjÛ7  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MNhju7  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¶6  h²hh³hÊh´Nubj”  )”}”(hX…  snapshot:
Will cause a snapshot to be triggered when the function is hit.
::

 echo 'native_flush_tlb_others:snapshot' > set_ftrace_filter

To only snapshot once:
::

 echo 'native_flush_tlb_others:snapshot:1' > set_ftrace_filter

To remove the above commands::

 echo '!native_flush_tlb_others:snapshot' > set_ftrace_filter
 echo '!native_flush_tlb_others:snapshot:0' > set_ftrace_filter
”h]”(hÌ)”}”(hŒLsnapshot:
Will cause a snapshot to be triggered when the function is hit.
::”h]”hŒIsnapshot:
Will cause a snapshot to be triggered when the function is hit.”…””}”(hjó7  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MPhjï7  ubj´  )”}”(hŒ;echo 'native_flush_tlb_others:snapshot' > set_ftrace_filter”h]”hŒ;echo 'native_flush_tlb_others:snapshot' > set_ftrace_filter”…””}”hj8  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MThjï7  ubhÌ)”}”(hŒTo only snapshot once:
::”h]”hŒTo only snapshot once:”…””}”(hj8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MVhjï7  ubj´  )”}”(hŒ=echo 'native_flush_tlb_others:snapshot:1' > set_ftrace_filter”h]”hŒ=echo 'native_flush_tlb_others:snapshot:1' > set_ftrace_filter”…””}”hj8  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MYhjï7  ubhÌ)”}”(hŒTo remove the above commands::”h]”hŒTo remove the above commands:”…””}”(hj+8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M[hjï7  ubj´  )”}”(hŒ{echo '!native_flush_tlb_others:snapshot' > set_ftrace_filter
echo '!native_flush_tlb_others:snapshot:0' > set_ftrace_filter”h]”hŒ{echo '!native_flush_tlb_others:snapshot' > set_ftrace_filter
echo '!native_flush_tlb_others:snapshot:0' > set_ftrace_filter”…””}”hj98  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M]hjï7  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¶6  h²hh³hÊh´Nubj”  )”}”(hX&  enable_event/disable_event:
These commands can enable or disable a trace event. Note, because
function tracing callbacks are very sensitive, when these commands
are registered, the trace point is activated, but disabled in
a "soft" mode. That is, the tracepoint will be called, but
just will not be traced. The event tracepoint stays in this mode
as long as there's a command that triggers it.
::

 echo 'try_to_wake_up:enable_event:sched:sched_switch:2' > \
       set_ftrace_filter

The format is::

  <function>:enable_event:<system>:<event>[:count]
  <function>:disable_event:<system>:<event>[:count]

To remove the events commands::

 echo '!try_to_wake_up:enable_event:sched:sched_switch:0' > \
       set_ftrace_filter
 echo '!schedule:disable_event:sched:sched_switch' > \
       set_ftrace_filter
”h]”(hÌ)”}”(hXŒ  enable_event/disable_event:
These commands can enable or disable a trace event. Note, because
function tracing callbacks are very sensitive, when these commands
are registered, the trace point is activated, but disabled in
a "soft" mode. That is, the tracepoint will be called, but
just will not be traced. The event tracepoint stays in this mode
as long as there's a command that triggers it.
::”h]”hX  enable_event/disable_event:
These commands can enable or disable a trace event. Note, because
function tracing callbacks are very sensitive, when these commands
are registered, the trace point is activated, but disabled in
a â€œsoftâ€ mode. That is, the tracepoint will be called, but
just will not be traced. The event tracepoint stays in this mode
as long as thereâ€™s a command that triggers it.”…””}”(hjQ8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M`hjM8  ubj´  )”}”(hŒSecho 'try_to_wake_up:enable_event:sched:sched_switch:2' > \
      set_ftrace_filter”h]”hŒSecho 'try_to_wake_up:enable_event:sched:sched_switch:2' > \
      set_ftrace_filter”…””}”hj_8  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MihjM8  ubhÌ)”}”(hŒThe format is::”h]”hŒThe format is:”…””}”(hjm8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MlhjM8  ubj´  )”}”(hŒb<function>:enable_event:<system>:<event>[:count]
<function>:disable_event:<system>:<event>[:count]”h]”hŒb<function>:enable_event:<system>:<event>[:count]
<function>:disable_event:<system>:<event>[:count]”…””}”hj{8  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MnhjM8  ubhÌ)”}”(hŒTo remove the events commands::”h]”hŒTo remove the events commands:”…””}”(hj‰8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MqhjM8  ubj´  )”}”(hŒ¢echo '!try_to_wake_up:enable_event:sched:sched_switch:0' > \
      set_ftrace_filter
echo '!schedule:disable_event:sched:sched_switch' > \
      set_ftrace_filter”h]”hŒ¢echo '!try_to_wake_up:enable_event:sched:sched_switch:0' > \
      set_ftrace_filter
echo '!schedule:disable_event:sched:sched_switch' > \
      set_ftrace_filter”…””}”hj—8  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MshjM8  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¶6  h²hh³hÊh´Nubj”  )”}”(hXA  dump:
When the function is hit, it will dump the contents of the ftrace
ring buffer to the console. This is useful if you need to debug
something, and want to dump the trace when a certain function
is hit. Perhaps it's a function that is called before a triple
fault happens and does not allow you to get a regular dump.
”h]”hÌ)”}”(hX@  dump:
When the function is hit, it will dump the contents of the ftrace
ring buffer to the console. This is useful if you need to debug
something, and want to dump the trace when a certain function
is hit. Perhaps it's a function that is called before a triple
fault happens and does not allow you to get a regular dump.”h]”hXB  dump:
When the function is hit, it will dump the contents of the ftrace
ring buffer to the console. This is useful if you need to debug
something, and want to dump the trace when a certain function
is hit. Perhaps itâ€™s a function that is called before a triple
fault happens and does not allow you to get a regular dump.”…””}”(hj¯8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mxhj«8  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¶6  h²hh³hÊh´Nubj”  )”}”(hX	  cpudump:
When the function is hit, it will dump the contents of the ftrace
ring buffer for the current CPU to the console. Unlike the "dump"
command, it only prints out the contents of the ring buffer for the
CPU that executed the function that triggered the dump.
”h]”hÌ)”}”(hX  cpudump:
When the function is hit, it will dump the contents of the ftrace
ring buffer for the current CPU to the console. Unlike the "dump"
command, it only prints out the contents of the ring buffer for the
CPU that executed the function that triggered the dump.”h]”hX  cpudump:
When the function is hit, it will dump the contents of the ftrace
ring buffer for the current CPU to the console. Unlike the â€œdumpâ€
command, it only prints out the contents of the ring buffer for the
CPU that executed the function that triggered the dump.”…””}”(hjÇ8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjÃ8  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¶6  h²hh³hÊh´Nubj”  )”}”(hŒAstacktrace:
When the function is hit, a stack trace is recorded.
”h]”hÌ)”}”(hŒ@stacktrace:
When the function is hit, a stack trace is recorded.”h]”hŒ@stacktrace:
When the function is hit, a stack trace is recorded.”…””}”(hjß8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M…hjÛ8  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j“  hj¶6  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jŽ  h³hÊh´Mhj{6  h²hubeh}”(h]”Œfilter-commands”ah ]”h"]”Œfilter commands”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mubh¶)”}”(hhh]”(h»)”}”(hŒ
trace_pipe”h]”hŒ
trace_pipe”…””}”(hj9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj9  h²hh³hÊh´M‰ubhÌ)”}”(hŒØThe trace_pipe outputs the same content as the trace file, but
the effect on the tracing is different. Every read from
trace_pipe is consumed. This means that subsequent reads will be
different. The trace is live.
::”h]”hŒÕThe trace_pipe outputs the same content as the trace file, but
the effect on the tracing is different. Every read from
trace_pipe is consumed. This means that subsequent reads will be
different. The trace is live.”…””}”(hj9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‹hj9  h²hubj´  )”}”(hX-  # echo function > current_tracer
# cat trace_pipe > /tmp/trace.out &
[1] 4153
# echo 1 > tracing_on
# usleep 1
# echo 0 > tracing_on
# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 0/0   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |

#
# cat /tmp/trace.out
           bash-1994  [000] ....  5281.568961: mutex_unlock <-rb_simple_write
           bash-1994  [000] ....  5281.568963: __mutex_unlock_slowpath <-mutex_unlock
           bash-1994  [000] ....  5281.568963: __fsnotify_parent <-fsnotify_modify
           bash-1994  [000] ....  5281.568964: fsnotify <-fsnotify_modify
           bash-1994  [000] ....  5281.568964: __srcu_read_lock <-fsnotify
           bash-1994  [000] ....  5281.568964: add_preempt_count <-__srcu_read_lock
           bash-1994  [000] ...1  5281.568965: sub_preempt_count <-__srcu_read_lock
           bash-1994  [000] ....  5281.568965: __srcu_read_unlock <-fsnotify
           bash-1994  [000] ....  5281.568967: sys_dup2 <-system_call_fastpath”h]”hX-  # echo function > current_tracer
# cat trace_pipe > /tmp/trace.out &
[1] 4153
# echo 1 > tracing_on
# usleep 1
# echo 0 > tracing_on
# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 0/0   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |

#
# cat /tmp/trace.out
           bash-1994  [000] ....  5281.568961: mutex_unlock <-rb_simple_write
           bash-1994  [000] ....  5281.568963: __mutex_unlock_slowpath <-mutex_unlock
           bash-1994  [000] ....  5281.568963: __fsnotify_parent <-fsnotify_modify
           bash-1994  [000] ....  5281.568964: fsnotify <-fsnotify_modify
           bash-1994  [000] ....  5281.568964: __srcu_read_lock <-fsnotify
           bash-1994  [000] ....  5281.568964: add_preempt_count <-__srcu_read_lock
           bash-1994  [000] ...1  5281.568965: sub_preempt_count <-__srcu_read_lock
           bash-1994  [000] ....  5281.568965: __srcu_read_unlock <-fsnotify
           bash-1994  [000] ....  5281.568967: sys_dup2 <-system_call_fastpath”…””}”hj 9  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M‘hj9  h²hubhÌ)”}”(hX  Note, reading the trace_pipe file will block until more input is
added. This is contrary to the trace file. If any process opened
the trace file for reading, it will actually disable tracing and
prevent new entries from being added. The trace_pipe file does
not have this limitation.”h]”hX  Note, reading the trace_pipe file will block until more input is
added. This is contrary to the trace file. If any process opened
the trace file for reading, it will actually disable tracing and
prevent new entries from being added. The trace_pipe file does
not have this limitation.”…””}”(hj.9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M±hj9  h²hubeh}”(h]”Œ
trace-pipe”ah ]”h"]”Œ
trace_pipe”ah$]”h&]”uh1hµhh·h²hh³hÊh´M‰ubh¶)”}”(hhh]”(h»)”}”(hŒtrace entries”h]”hŒtrace entries”…””}”(hjG9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjD9  h²hh³hÊh´M¸ubhÌ)”}”(hXQ  Having too much or not enough data can be troublesome in
diagnosing an issue in the kernel. The file buffer_size_kb is
used to modify the size of the internal trace buffers. The
number listed is the number of entries that can be recorded per
CPU. To know the full size, multiply the number of possible CPUs
with the number of entries.
::”h]”hXN  Having too much or not enough data can be troublesome in
diagnosing an issue in the kernel. The file buffer_size_kb is
used to modify the size of the internal trace buffers. The
number listed is the number of entries that can be recorded per
CPU. To know the full size, multiply the number of possible CPUs
with the number of entries.”…””}”(hjU9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MºhjD9  h²hubj´  )”}”(hŒ+# cat buffer_size_kb
1408 (units kilobytes)”h]”hŒ+# cat buffer_size_kb
1408 (units kilobytes)”…””}”hjc9  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÂhjD9  h²hubhÌ)”}”(hŒ&Or simply read buffer_total_size_kb
::”h]”hŒ#Or simply read buffer_total_size_kb”…””}”(hjq9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÅhjD9  h²hubj´  )”}”(hŒ# cat buffer_total_size_kb
5632”h]”hŒ# cat buffer_total_size_kb
5632”…””}”hj9  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÈhjD9  h²hubhÌ)”}”(hŒITo modify the buffer, simple echo in a number (in 1024 byte segments).
::”h]”hŒFTo modify the buffer, simple echo in a number (in 1024 byte segments).”…””}”(hj9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MËhjD9  h²hubj´  )”}”(hŒJ# echo 10000 > buffer_size_kb
# cat buffer_size_kb
10000 (units kilobytes)”h]”hŒJ# echo 10000 > buffer_size_kb
# cat buffer_size_kb
10000 (units kilobytes)”…””}”hj›9  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÎhjD9  h²hubhÌ)”}”(hŒpIt will try to allocate as much as possible. If you allocate too
much, it can cause Out-Of-Memory to trigger.
::”h]”hŒmIt will try to allocate as much as possible. If you allocate too
much, it can cause Out-Of-Memory to trigger.”…””}”(hj©9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÒhjD9  h²hubj´  )”}”(hŒn# echo 1000000000000 > buffer_size_kb
-bash: echo: write error: Cannot allocate memory
# cat buffer_size_kb
85”h]”hŒn# echo 1000000000000 > buffer_size_kb
-bash: echo: write error: Cannot allocate memory
# cat buffer_size_kb
85”…””}”hj·9  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÖhjD9  h²hubhÌ)”}”(hŒ;The per_cpu buffers can be changed individually as well:
::”h]”hŒ8The per_cpu buffers can be changed individually as well:”…””}”(hjÅ9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÛhjD9  h²hubj´  )”}”(hŒS# echo 10000 > per_cpu/cpu0/buffer_size_kb
# echo 100 > per_cpu/cpu1/buffer_size_kb”h]”hŒS# echo 10000 > per_cpu/cpu0/buffer_size_kb
# echo 100 > per_cpu/cpu1/buffer_size_kb”…””}”hjÓ9  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÞhjD9  h²hubhÌ)”}”(hŒeWhen the per_cpu buffers are not the same, the buffer_size_kb
at the top level will just show an X
::”h]”hŒbWhen the per_cpu buffers are not the same, the buffer_size_kb
at the top level will just show an X”…””}”(hjá9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MáhjD9  h²hubj´  )”}”(hŒ# cat buffer_size_kb
X”h]”hŒ# cat buffer_size_kb
X”…””}”hjï9  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MåhjD9  h²hubhÌ)”}”(hŒ4This is where the buffer_total_size_kb is useful:
::”h]”hŒ1This is where the buffer_total_size_kb is useful:”…””}”(hjý9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MèhjD9  h²hubj´  )”}”(hŒ # cat buffer_total_size_kb
12916”h]”hŒ # cat buffer_total_size_kb
12916”…””}”hj:  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MëhjD9  h²hubhÌ)”}”(hŒXWriting to the top level buffer_size_kb will reset all the buffers
to be the same again.”h]”hŒXWriting to the top level buffer_size_kb will reset all the buffers
to be the same again.”…””}”(hj:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MîhjD9  h²hubeh}”(h]”Œtrace-entries”ah ]”h"]”Œtrace entries”ah$]”h&]”uh1hµhh·h²hh³hÊh´M¸ubh¶)”}”(hhh]”(h»)”}”(hŒSnapshot”h]”hŒSnapshot”…””}”(hj2:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj/:  h²hh³hÊh´MòubhÌ)”}”(hX  CONFIG_TRACER_SNAPSHOT makes a generic snapshot feature
available to all non latency tracers. (Latency tracers which
record max latency, such as "irqsoff" or "wakeup", can't use
this feature, since those are already using the snapshot
mechanism internally.)”h]”hX  CONFIG_TRACER_SNAPSHOT makes a generic snapshot feature
available to all non latency tracers. (Latency tracers which
record max latency, such as â€œirqsoffâ€ or â€œwakeupâ€, canâ€™t use
this feature, since those are already using the snapshot
mechanism internally.)”…””}”(hj@:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Móhj/:  h²hubhÌ)”}”(hŒÙSnapshot preserves a current trace buffer at a particular point
in time without stopping tracing. Ftrace swaps the current
buffer with a spare buffer, and tracing continues in the new
current (=previous spare) buffer.”h]”hŒÙSnapshot preserves a current trace buffer at a particular point
in time without stopping tracing. Ftrace swaps the current
buffer with a spare buffer, and tracing continues in the new
current (=previous spare) buffer.”…””}”(hjN:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mùhj/:  h²hubhÌ)”}”(hŒEThe following tracefs files in "tracing" are related to this
feature:”h]”hŒIThe following tracefs files in â€œtracingâ€ are related to this
feature:”…””}”(hj\:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mþhj/:  h²hubjh  )”}”(hXé  snapshot:

      This is used to take a snapshot and to read the output
      of the snapshot. Echo 1 into this file to allocate a
      spare buffer and to take a snapshot (swap), then read
      the snapshot from this file in the same format as
      "trace" (described above in the section "The File
      System"). Both reads snapshot and tracing are executable
      in parallel. When the spare buffer is allocated, echoing
      0 frees it, and echoing else (positive) values clear the
      snapshot contents.
      More details are shown in the table below.

      +--------------+------------+------------+------------+
      |status\\input |     0      |     1      |    else    |
      +==============+============+============+============+
      |not allocated |(do nothing)| alloc+swap |(do nothing)|
      +--------------+------------+------------+------------+
      |allocated     |    free    |    swap    |   clear    |
      +--------------+------------+------------+------------+
”h]”(hÌ)”}”(hŒ	snapshot:”h]”hŒ	snapshot:”…””}”(hjn:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjj:  ubjh  )”}”(hXx  This is used to take a snapshot and to read the output
of the snapshot. Echo 1 into this file to allocate a
spare buffer and to take a snapshot (swap), then read
the snapshot from this file in the same format as
"trace" (described above in the section "The File
System"). Both reads snapshot and tracing are executable
in parallel. When the spare buffer is allocated, echoing
0 frees it, and echoing else (positive) values clear the
snapshot contents.
More details are shown in the table below.

+--------------+------------+------------+------------+
|status\\input |     0      |     1      |    else    |
+==============+============+============+============+
|not allocated |(do nothing)| alloc+swap |(do nothing)|
+--------------+------------+------------+------------+
|allocated     |    free    |    swap    |   clear    |
+--------------+------------+------------+------------+
”h]”(hÌ)”}”(hXî  This is used to take a snapshot and to read the output
of the snapshot. Echo 1 into this file to allocate a
spare buffer and to take a snapshot (swap), then read
the snapshot from this file in the same format as
"trace" (described above in the section "The File
System"). Both reads snapshot and tracing are executable
in parallel. When the spare buffer is allocated, echoing
0 frees it, and echoing else (positive) values clear the
snapshot contents.
More details are shown in the table below.”h]”hXö  This is used to take a snapshot and to read the output
of the snapshot. Echo 1 into this file to allocate a
spare buffer and to take a snapshot (swap), then read
the snapshot from this file in the same format as
â€œtraceâ€ (described above in the section â€œThe File
Systemâ€). Both reads snapshot and tracing are executable
in parallel. When the spare buffer is allocated, echoing
0 frees it, and echoing else (positive) values clear the
snapshot contents.
More details are shown in the table below.”…””}”(hj€:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj|:  ubhŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j˜:  hj•:  ubj™:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j˜:  hj•:  ubj™:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j˜:  hj•:  ubj™:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j˜:  hj•:  ubhŒthead”“”)”}”(hhh]”hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hÌ)”}”(hŒstatus\\input”h]”hŒstatus \input”…””}”(hjÑ:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjÎ:  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hjÉ:  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒ0”h]”hŒ0”…””}”(hjè:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjå:  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hjÉ:  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒ1”h]”hŒ1”…””}”(hjÿ:  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjü:  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hjÉ:  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒelse”h]”hŒelse”…””}”(hj;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hjÉ:  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÇ:  hjÄ:  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÂ:  hj•:  ubhŒtbody”“”)”}”(hhh]”(jÈ:  )”}”(hhh]”(jÍ:  )”}”(hhh]”hÌ)”}”(hŒnot allocated”h]”hŒnot allocated”…””}”(hjA;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj>;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj;;  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒ(do nothing)”h]”hŒ(do nothing)”…””}”(hjX;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjU;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj;;  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒ
alloc+swap”h]”hŒ
alloc+swap”…””}”(hjo;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjl;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj;;  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒ(do nothing)”h]”hŒ(do nothing)”…””}”(hj†;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjƒ;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj;;  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÇ:  hj8;  ubjÈ:  )”}”(hhh]”(jÍ:  )”}”(hhh]”hÌ)”}”(hŒ	allocated”h]”hŒ	allocated”…””}”(hj¦;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj£;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj ;  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒfree”h]”hŒfree”…””}”(hj½;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjº;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj ;  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒswap”h]”hŒswap”…””}”(hjÔ;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MhjÑ;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj ;  ubjÍ:  )”}”(hhh]”hÌ)”}”(hŒclear”h]”hŒclear”…””}”(hjë;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjè;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ:  hj ;  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÇ:  hj8;  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j6;  hj•:  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j“:  hj:  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŽ:  hj|:  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhjj:  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jg  h³hÊh´Mhj/:  h²hubhÌ)”}”(hŒ4Here is an example of using the snapshot feature.
::”h]”hŒ1Here is an example of using the snapshot feature.”…””}”(hj$<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj/:  h²hubj´  )”}”(hX=  # echo 1 > events/sched/enable
# echo 1 > snapshot
# cat snapshot
# tracer: nop
#
# entries-in-buffer/entries-written: 71/71   #P:8
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          <idle>-0     [005] d...  2440.603828: sched_switch: prev_comm=swapper/5 prev_pid=0 prev_prio=120   prev_state=R ==> next_comm=snapshot-test-2 next_pid=2242 next_prio=120
           sleep-2242  [005] d...  2440.603846: sched_switch: prev_comm=snapshot-test-2 prev_pid=2242 prev_prio=120   prev_state=R ==> next_comm=kworker/5:1 next_pid=60 next_prio=120
[...]
        <idle>-0     [002] d...  2440.707230: sched_switch: prev_comm=swapper/2 prev_pid=0 prev_prio=120 prev_state=R ==> next_comm=snapshot-test-2 next_pid=2229 next_prio=120

# cat trace
# tracer: nop
#
# entries-in-buffer/entries-written: 77/77   #P:8
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          <idle>-0     [007] d...  2440.707395: sched_switch: prev_comm=swapper/7 prev_pid=0 prev_prio=120 prev_state=R ==> next_comm=snapshot-test-2 next_pid=2243 next_prio=120
 snapshot-test-2-2229  [002] d...  2440.707438: sched_switch: prev_comm=snapshot-test-2 prev_pid=2229 prev_prio=120 prev_state=S ==> next_comm=swapper/2 next_pid=0 next_prio=120
[...]”h]”hX=  # echo 1 > events/sched/enable
# echo 1 > snapshot
# cat snapshot
# tracer: nop
#
# entries-in-buffer/entries-written: 71/71   #P:8
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          <idle>-0     [005] d...  2440.603828: sched_switch: prev_comm=swapper/5 prev_pid=0 prev_prio=120   prev_state=R ==> next_comm=snapshot-test-2 next_pid=2242 next_prio=120
           sleep-2242  [005] d...  2440.603846: sched_switch: prev_comm=snapshot-test-2 prev_pid=2242 prev_prio=120   prev_state=R ==> next_comm=kworker/5:1 next_pid=60 next_prio=120
[...]
        <idle>-0     [002] d...  2440.707230: sched_switch: prev_comm=swapper/2 prev_pid=0 prev_prio=120 prev_state=R ==> next_comm=snapshot-test-2 next_pid=2229 next_prio=120

# cat trace
# tracer: nop
#
# entries-in-buffer/entries-written: 77/77   #P:8
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
          <idle>-0     [007] d...  2440.707395: sched_switch: prev_comm=swapper/7 prev_pid=0 prev_prio=120 prev_state=R ==> next_comm=snapshot-test-2 next_pid=2243 next_prio=120
 snapshot-test-2-2229  [002] d...  2440.707438: sched_switch: prev_comm=snapshot-test-2 prev_pid=2229 prev_prio=120 prev_state=S ==> next_comm=swapper/2 next_pid=0 next_prio=120
[...]”…””}”hj2<  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mhj/:  h²hubhÌ)”}”(hŒIf you try to use this snapshot feature when current tracer is
one of the latency tracers, you will get the following results.
::”h]”hŒ~If you try to use this snapshot feature when current tracer is
one of the latency tracers, you will get the following results.”…””}”(hj@<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M=hj/:  h²hubj´  )”}”(hŒ™# echo wakeup > current_tracer
# echo 1 > snapshot
bash: echo: write error: Device or resource busy
# cat snapshot
cat: snapshot: Device or resource busy”h]”hŒ™# echo wakeup > current_tracer
# echo 1 > snapshot
bash: echo: write error: Device or resource busy
# cat snapshot
cat: snapshot: Device or resource busy”…””}”hjN<  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MAhj/:  h²hubeh}”(h]”Œsnapshot”ah ]”h"]”Œsnapshot”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mòubh¶)”}”(hhh]”(h»)”}”(hŒ	Instances”h]”hŒ	Instances”…””}”(hjg<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjd<  h²hh³hÊh´MIubhÌ)”}”(hX5  In the tracefs tracing directory, there is a directory called "instances".
This directory can have new directories created inside of it using
mkdir, and removing directories with rmdir. The directory created
with mkdir in this directory will already contain files and other
directories after it is created.
::”h]”hX6  In the tracefs tracing directory, there is a directory called â€œinstancesâ€.
This directory can have new directories created inside of it using
mkdir, and removing directories with rmdir. The directory created
with mkdir in this directory will already contain files and other
directories after it is created.”…””}”(hju<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MJhjd<  h²hubj´  )”}”(hŒÇ# mkdir instances/foo
# ls instances/foo
buffer_size_kb  buffer_total_size_kb  events  free_buffer  per_cpu
set_event  snapshot  trace  trace_clock  trace_marker  trace_options
trace_pipe  tracing_on”h]”hŒÇ# mkdir instances/foo
# ls instances/foo
buffer_size_kb  buffer_total_size_kb  events  free_buffer  per_cpu
set_event  snapshot  trace  trace_clock  trace_marker  trace_options
trace_pipe  tracing_on”…””}”hjƒ<  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MQhjd<  h²hubhÌ)”}”(hŒãAs you can see, the new directory looks similar to the tracing directory
itself. In fact, it is very similar, except that the buffer and
events are agnostic from the main directory, or from any other
instances that are created.”h]”hŒãAs you can see, the new directory looks similar to the tracing directory
itself. In fact, it is very similar, except that the buffer and
events are agnostic from the main directory, or from any other
instances that are created.”…””}”(hj‘<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MWhjd<  h²hubhÌ)”}”(hXÆ  The files in the new directory work just like the files with the
same name in the tracing directory except the buffer that is used
is a separate and new buffer. The files affect that buffer but do not
affect the main buffer with the exception of trace_options. Currently,
the trace_options affect all instances and the top level buffer
the same, but this may change in future releases. That is, options
may become specific to the instance they reside in.”h]”hXÆ  The files in the new directory work just like the files with the
same name in the tracing directory except the buffer that is used
is a separate and new buffer. The files affect that buffer but do not
affect the main buffer with the exception of trace_options. Currently,
the trace_options affect all instances and the top level buffer
the same, but this may change in future releases. That is, options
may become specific to the instance they reside in.”…””}”(hjŸ<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M\hjd<  h²hubhÌ)”}”(hŒµNotice that none of the function tracer files are there, nor is
current_tracer and available_tracers. This is because the buffers
can currently only have events enabled for them.
::”h]”hŒ²Notice that none of the function tracer files are there, nor is
current_tracer and available_tracers. This is because the buffers
can currently only have events enabled for them.”…””}”(hj­<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mdhjd<  h²hubj´  )”}”(hXÞ  # mkdir instances/foo
# mkdir instances/bar
# mkdir instances/zoot
# echo 100000 > buffer_size_kb
# echo 1000 > instances/foo/buffer_size_kb
# echo 5000 > instances/bar/per_cpu/cpu1/buffer_size_kb
# echo function > current_trace
# echo 1 > instances/foo/events/sched/sched_wakeup/enable
# echo 1 > instances/foo/events/sched/sched_wakeup_new/enable
# echo 1 > instances/foo/events/sched/sched_switch/enable
# echo 1 > instances/bar/events/irq/enable
# echo 1 > instances/zoot/events/syscalls/enable
# cat trace_pipe
CPU:2 [LOST 11745 EVENTS]
            bash-2044  [002] .... 10594.481032: _raw_spin_lock_irqsave <-get_page_from_freelist
            bash-2044  [002] d... 10594.481032: add_preempt_count <-_raw_spin_lock_irqsave
            bash-2044  [002] d..1 10594.481032: __rmqueue <-get_page_from_freelist
            bash-2044  [002] d..1 10594.481033: _raw_spin_unlock <-get_page_from_freelist
            bash-2044  [002] d..1 10594.481033: sub_preempt_count <-_raw_spin_unlock
            bash-2044  [002] d... 10594.481033: get_pageblock_flags_group <-get_pageblock_migratetype
            bash-2044  [002] d... 10594.481034: __mod_zone_page_state <-get_page_from_freelist
            bash-2044  [002] d... 10594.481034: zone_statistics <-get_page_from_freelist
            bash-2044  [002] d... 10594.481034: __inc_zone_state <-zone_statistics
            bash-2044  [002] d... 10594.481034: __inc_zone_state <-zone_statistics
            bash-2044  [002] .... 10594.481035: arch_dup_task_struct <-copy_process
[...]

# cat instances/foo/trace_pipe
            bash-1998  [000] d..4   136.676759: sched_wakeup: comm=kworker/0:1 pid=59 prio=120 success=1 target_cpu=000
            bash-1998  [000] dN.4   136.676760: sched_wakeup: comm=bash pid=1998 prio=120 success=1 target_cpu=000
          <idle>-0     [003] d.h3   136.676906: sched_wakeup: comm=rcu_preempt pid=9 prio=120 success=1 target_cpu=003
          <idle>-0     [003] d..3   136.676909: sched_switch: prev_comm=swapper/3 prev_pid=0 prev_prio=120 prev_state=R ==> next_comm=rcu_preempt next_pid=9 next_prio=120
     rcu_preempt-9     [003] d..3   136.676916: sched_switch: prev_comm=rcu_preempt prev_pid=9 prev_prio=120 prev_state=S ==> next_comm=swapper/3 next_pid=0 next_prio=120
            bash-1998  [000] d..4   136.677014: sched_wakeup: comm=kworker/0:1 pid=59 prio=120 success=1 target_cpu=000
            bash-1998  [000] dN.4   136.677016: sched_wakeup: comm=bash pid=1998 prio=120 success=1 target_cpu=000
            bash-1998  [000] d..3   136.677018: sched_switch: prev_comm=bash prev_pid=1998 prev_prio=120 prev_state=R+ ==> next_comm=kworker/0:1 next_pid=59 next_prio=120
     kworker/0:1-59    [000] d..4   136.677022: sched_wakeup: comm=sshd pid=1995 prio=120 success=1 target_cpu=001
     kworker/0:1-59    [000] d..3   136.677025: sched_switch: prev_comm=kworker/0:1 prev_pid=59 prev_prio=120 prev_state=S ==> next_comm=bash next_pid=1998 next_prio=120
[...]

# cat instances/bar/trace_pipe
     migration/1-14    [001] d.h3   138.732674: softirq_raise: vec=3 [action=NET_RX]
          <idle>-0     [001] dNh3   138.732725: softirq_raise: vec=3 [action=NET_RX]
            bash-1998  [000] d.h1   138.733101: softirq_raise: vec=1 [action=TIMER]
            bash-1998  [000] d.h1   138.733102: softirq_raise: vec=9 [action=RCU]
            bash-1998  [000] ..s2   138.733105: softirq_entry: vec=1 [action=TIMER]
            bash-1998  [000] ..s2   138.733106: softirq_exit: vec=1 [action=TIMER]
            bash-1998  [000] ..s2   138.733106: softirq_entry: vec=9 [action=RCU]
            bash-1998  [000] ..s2   138.733109: softirq_exit: vec=9 [action=RCU]
            sshd-1995  [001] d.h1   138.733278: irq_handler_entry: irq=21 name=uhci_hcd:usb4
            sshd-1995  [001] d.h1   138.733280: irq_handler_exit: irq=21 ret=unhandled
            sshd-1995  [001] d.h1   138.733281: irq_handler_entry: irq=21 name=eth0
            sshd-1995  [001] d.h1   138.733283: irq_handler_exit: irq=21 ret=handled
[...]

# cat instances/zoot/trace
# tracer: nop
#
# entries-in-buffer/entries-written: 18996/18996   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1998  [000] d...   140.733501: sys_write -> 0x2
            bash-1998  [000] d...   140.733504: sys_dup2(oldfd: a, newfd: 1)
            bash-1998  [000] d...   140.733506: sys_dup2 -> 0x1
            bash-1998  [000] d...   140.733508: sys_fcntl(fd: a, cmd: 1, arg: 0)
            bash-1998  [000] d...   140.733509: sys_fcntl -> 0x1
            bash-1998  [000] d...   140.733510: sys_close(fd: a)
            bash-1998  [000] d...   140.733510: sys_close -> 0x0
            bash-1998  [000] d...   140.733514: sys_rt_sigprocmask(how: 0, nset: 0, oset: 6e2768, sigsetsize: 8)
            bash-1998  [000] d...   140.733515: sys_rt_sigprocmask -> 0x0
            bash-1998  [000] d...   140.733516: sys_rt_sigaction(sig: 2, act: 7fff718846f0, oact: 7fff71884650, sigsetsize: 8)
            bash-1998  [000] d...   140.733516: sys_rt_sigaction -> 0x0”h]”hXÞ  # mkdir instances/foo
# mkdir instances/bar
# mkdir instances/zoot
# echo 100000 > buffer_size_kb
# echo 1000 > instances/foo/buffer_size_kb
# echo 5000 > instances/bar/per_cpu/cpu1/buffer_size_kb
# echo function > current_trace
# echo 1 > instances/foo/events/sched/sched_wakeup/enable
# echo 1 > instances/foo/events/sched/sched_wakeup_new/enable
# echo 1 > instances/foo/events/sched/sched_switch/enable
# echo 1 > instances/bar/events/irq/enable
# echo 1 > instances/zoot/events/syscalls/enable
# cat trace_pipe
CPU:2 [LOST 11745 EVENTS]
            bash-2044  [002] .... 10594.481032: _raw_spin_lock_irqsave <-get_page_from_freelist
            bash-2044  [002] d... 10594.481032: add_preempt_count <-_raw_spin_lock_irqsave
            bash-2044  [002] d..1 10594.481032: __rmqueue <-get_page_from_freelist
            bash-2044  [002] d..1 10594.481033: _raw_spin_unlock <-get_page_from_freelist
            bash-2044  [002] d..1 10594.481033: sub_preempt_count <-_raw_spin_unlock
            bash-2044  [002] d... 10594.481033: get_pageblock_flags_group <-get_pageblock_migratetype
            bash-2044  [002] d... 10594.481034: __mod_zone_page_state <-get_page_from_freelist
            bash-2044  [002] d... 10594.481034: zone_statistics <-get_page_from_freelist
            bash-2044  [002] d... 10594.481034: __inc_zone_state <-zone_statistics
            bash-2044  [002] d... 10594.481034: __inc_zone_state <-zone_statistics
            bash-2044  [002] .... 10594.481035: arch_dup_task_struct <-copy_process
[...]

# cat instances/foo/trace_pipe
            bash-1998  [000] d..4   136.676759: sched_wakeup: comm=kworker/0:1 pid=59 prio=120 success=1 target_cpu=000
            bash-1998  [000] dN.4   136.676760: sched_wakeup: comm=bash pid=1998 prio=120 success=1 target_cpu=000
          <idle>-0     [003] d.h3   136.676906: sched_wakeup: comm=rcu_preempt pid=9 prio=120 success=1 target_cpu=003
          <idle>-0     [003] d..3   136.676909: sched_switch: prev_comm=swapper/3 prev_pid=0 prev_prio=120 prev_state=R ==> next_comm=rcu_preempt next_pid=9 next_prio=120
     rcu_preempt-9     [003] d..3   136.676916: sched_switch: prev_comm=rcu_preempt prev_pid=9 prev_prio=120 prev_state=S ==> next_comm=swapper/3 next_pid=0 next_prio=120
            bash-1998  [000] d..4   136.677014: sched_wakeup: comm=kworker/0:1 pid=59 prio=120 success=1 target_cpu=000
            bash-1998  [000] dN.4   136.677016: sched_wakeup: comm=bash pid=1998 prio=120 success=1 target_cpu=000
            bash-1998  [000] d..3   136.677018: sched_switch: prev_comm=bash prev_pid=1998 prev_prio=120 prev_state=R+ ==> next_comm=kworker/0:1 next_pid=59 next_prio=120
     kworker/0:1-59    [000] d..4   136.677022: sched_wakeup: comm=sshd pid=1995 prio=120 success=1 target_cpu=001
     kworker/0:1-59    [000] d..3   136.677025: sched_switch: prev_comm=kworker/0:1 prev_pid=59 prev_prio=120 prev_state=S ==> next_comm=bash next_pid=1998 next_prio=120
[...]

# cat instances/bar/trace_pipe
     migration/1-14    [001] d.h3   138.732674: softirq_raise: vec=3 [action=NET_RX]
          <idle>-0     [001] dNh3   138.732725: softirq_raise: vec=3 [action=NET_RX]
            bash-1998  [000] d.h1   138.733101: softirq_raise: vec=1 [action=TIMER]
            bash-1998  [000] d.h1   138.733102: softirq_raise: vec=9 [action=RCU]
            bash-1998  [000] ..s2   138.733105: softirq_entry: vec=1 [action=TIMER]
            bash-1998  [000] ..s2   138.733106: softirq_exit: vec=1 [action=TIMER]
            bash-1998  [000] ..s2   138.733106: softirq_entry: vec=9 [action=RCU]
            bash-1998  [000] ..s2   138.733109: softirq_exit: vec=9 [action=RCU]
            sshd-1995  [001] d.h1   138.733278: irq_handler_entry: irq=21 name=uhci_hcd:usb4
            sshd-1995  [001] d.h1   138.733280: irq_handler_exit: irq=21 ret=unhandled
            sshd-1995  [001] d.h1   138.733281: irq_handler_entry: irq=21 name=eth0
            sshd-1995  [001] d.h1   138.733283: irq_handler_exit: irq=21 ret=handled
[...]

# cat instances/zoot/trace
# tracer: nop
#
# entries-in-buffer/entries-written: 18996/18996   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
            bash-1998  [000] d...   140.733501: sys_write -> 0x2
            bash-1998  [000] d...   140.733504: sys_dup2(oldfd: a, newfd: 1)
            bash-1998  [000] d...   140.733506: sys_dup2 -> 0x1
            bash-1998  [000] d...   140.733508: sys_fcntl(fd: a, cmd: 1, arg: 0)
            bash-1998  [000] d...   140.733509: sys_fcntl -> 0x1
            bash-1998  [000] d...   140.733510: sys_close(fd: a)
            bash-1998  [000] d...   140.733510: sys_close -> 0x0
            bash-1998  [000] d...   140.733514: sys_rt_sigprocmask(how: 0, nset: 0, oset: 6e2768, sigsetsize: 8)
            bash-1998  [000] d...   140.733515: sys_rt_sigprocmask -> 0x0
            bash-1998  [000] d...   140.733516: sys_rt_sigaction(sig: 2, act: 7fff718846f0, oact: 7fff71884650, sigsetsize: 8)
            bash-1998  [000] d...   140.733516: sys_rt_sigaction -> 0x0”…””}”hj»<  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mihjd<  h²hubhÌ)”}”(hŒYou can see that the trace of the top most trace buffer shows only
the function tracing. The foo instance displays wakeups and task
switches.”h]”hŒYou can see that the trace of the top most trace buffer shows only
the function tracing. The foo instance displays wakeups and task
switches.”…””}”(hjÉ<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¸hjd<  h²hubhÌ)”}”(hŒ<To remove the instances, simply delete their directories:
::”h]”hŒ9To remove the instances, simply delete their directories:”…””}”(hj×<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¼hjd<  h²hubj´  )”}”(hŒB# rmdir instances/foo
# rmdir instances/bar
# rmdir instances/zoot”h]”hŒB# rmdir instances/foo
# rmdir instances/bar
# rmdir instances/zoot”…””}”hjå<  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´M¿hjd<  h²hubhÌ)”}”(hŒlNote, if a process has a trace file open in one of the instance
directories, the rmdir will fail with EBUSY.”h]”hŒlNote, if a process has a trace file open in one of the instance
directories, the rmdir will fail with EBUSY.”…””}”(hjó<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÃhjd<  h²hubeh}”(h]”Œ	instances”ah ]”h"]”Œ	instances”ah$]”h&]”uh1hµhh·h²hh³hÊh´MIubh¶)”}”(hhh]”(h»)”}”(hŒStack trace”h]”hŒStack trace”…””}”(hj=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj	=  h²hh³hÊh´MÈubhÌ)”}”(hX%  Since the kernel has a fixed sized stack, it is important not to
waste it in functions. A kernel developer must be conscious of
what they allocate on the stack. If they add too much, the system
can be in danger of a stack overflow, and corruption will occur,
usually leading to a system panic.”h]”hX%  Since the kernel has a fixed sized stack, it is important not to
waste it in functions. A kernel developer must be conscious of
what they allocate on the stack. If they add too much, the system
can be in danger of a stack overflow, and corruption will occur,
usually leading to a system panic.”…””}”(hj=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÉhj	=  h²hubhÌ)”}”(hXA  There are some tools that check this, usually with interrupts
periodically checking usage. But if you can perform a check
at every function call that will become very useful. As ftrace provides
a function tracer, it makes it convenient to check the stack size
at every function call. This is enabled via the stack tracer.”h]”hXA  There are some tools that check this, usually with interrupts
periodically checking usage. But if you can perform a check
at every function call that will become very useful. As ftrace provides
a function tracer, it makes it convenient to check the stack size
at every function call. This is enabled via the stack tracer.”…””}”(hj(=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÏhj	=  h²hubhÌ)”}”(hŒŒCONFIG_STACK_TRACER enables the ftrace stack tracing functionality.
To enable it, write a '1' into /proc/sys/kernel/stack_tracer_enabled.
::”h]”hŒCONFIG_STACK_TRACER enables the ftrace stack tracing functionality.
To enable it, write a â€˜1â€™ into /proc/sys/kernel/stack_tracer_enabled.”…””}”(hj6=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÕhj	=  h²hubj´  )”}”(hŒ0# echo 1 > /proc/sys/kernel/stack_tracer_enabled”h]”hŒ0# echo 1 > /proc/sys/kernel/stack_tracer_enabled”…””}”hjD=  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´MÙhj	=  h²hubhÌ)”}”(hŒ¦You can also enable it from the kernel command line to trace
the stack size of the kernel during boot up, by adding "stacktrace"
to the kernel command line parameter.”h]”hŒªYou can also enable it from the kernel command line to trace
the stack size of the kernel during boot up, by adding â€œstacktraceâ€
to the kernel command line parameter.”…””}”(hjR=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÛhj	=  h²hubhÌ)”}”(hŒ=After running it for a few minutes, the output looks like:
::”h]”hŒ:After running it for a few minutes, the output looks like:”…””}”(hj`=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mßhj	=  h²hubj´  )”}”(hXõ  # cat stack_max_size
2928

# cat stack_trace
        Depth    Size   Location    (18 entries)
        -----    ----   --------
  0)     2928     224   update_sd_lb_stats+0xbc/0x4ac
  1)     2704     160   find_busiest_group+0x31/0x1f1
  2)     2544     256   load_balance+0xd9/0x662
  3)     2288      80   idle_balance+0xbb/0x130
  4)     2208     128   __schedule+0x26e/0x5b9
  5)     2080      16   schedule+0x64/0x66
  6)     2064     128   schedule_timeout+0x34/0xe0
  7)     1936     112   wait_for_common+0x97/0xf1
  8)     1824      16   wait_for_completion+0x1d/0x1f
  9)     1808     128   flush_work+0xfe/0x119
 10)     1680      16   tty_flush_to_ldisc+0x1e/0x20
 11)     1664      48   input_available_p+0x1d/0x5c
 12)     1616      48   n_tty_poll+0x6d/0x134
 13)     1568      64   tty_poll+0x64/0x7f
 14)     1504     880   do_select+0x31e/0x511
 15)      624     400   core_sys_select+0x177/0x216
 16)      224      96   sys_select+0x91/0xb9
 17)      128     128   system_call_fastpath+0x16/0x1b”•R(      h]”hXõ  # cat stack_max_size
2928

# cat stack_trace
        Depth    Size   Location    (18 entries)
        -----    ----   --------
  0)     2928     224   update_sd_lb_stats+0xbc/0x4ac
  1)     2704     160   find_busiest_group+0x31/0x1f1
  2)     2544     256   load_balance+0xd9/0x662
  3)     2288      80   idle_balance+0xbb/0x130
  4)     2208     128   __schedule+0x26e/0x5b9
  5)     2080      16   schedule+0x64/0x66
  6)     2064     128   schedule_timeout+0x34/0xe0
  7)     1936     112   wait_for_common+0x97/0xf1
  8)     1824      16   wait_for_completion+0x1d/0x1f
  9)     1808     128   flush_work+0xfe/0x119
 10)     1680      16   tty_flush_to_ldisc+0x1e/0x20
 11)     1664      48   input_available_p+0x1d/0x5c
 12)     1616      48   n_tty_poll+0x6d/0x134
 13)     1568      64   tty_poll+0x64/0x7f
 14)     1504     880   do_select+0x31e/0x511
 15)      624     400   core_sys_select+0x177/0x216
 16)      224      96   sys_select+0x91/0xb9
 17)      128     128   system_call_fastpath+0x16/0x1b”…””}”hjn=  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  h³hÊh´Mâhj	=  h²hubhÌ)”}”(hŒ¿Note, if -mfentry is being used by gcc, functions get traced before
they set up the stack frame. This means that leaf level functions
are not tested by the stack tracer when -mfentry is used.”h]”hŒ¿Note, if -mfentry is being used by gcc, functions get traced before
they set up the stack frame. This means that leaf level functions
are not tested by the stack tracer when -mfentry is used.”…””}”(hj|=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mûhj	=  h²hubhÌ)”}”(hŒ?Currently, -mfentry is used by gcc 4.6.0 and above on x86 only.”h]”hŒ?Currently, -mfentry is used by gcc 4.6.0 and above on x86 only.”…””}”(hjŠ=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mÿhj	=  h²hubeh}”(h]”Œstack-trace”ah ]”h"]”Œstack trace”ah$]”h&]”uh1hµhh·h²hh³hÊh´MÈubh¶)”}”(hhh]”(h»)”}”(hŒMore”h]”hŒMore”…””}”(hj£=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj =  h²hh³hÊh´MubhÌ)”}”(hŒNMore details can be found in the source code, in the `kernel/trace/*.c` files.”h]”(hŒ5More details can be found in the source code, in the ”…””}”(hj±=  h²hh³Nh´NubhŒtitle_reference”“”)”}”(hŒ`kernel/trace/*.c`”h]”hŒkernel/trace/*.c”…””}”(hj»=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¹=  hj±=  ubhŒ files.”…””}”(hj±=  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj =  h²hubeh}”(h]”Œmore”ah ]”h"]”Œmore”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mubeh}”(h]”Œftrace-function-tracer”ah ]”h"]”Œftrace - function tracer”ah$]”h&]”uh1hµhhh²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”jÌ:  Œ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”j>  Œ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”}”(jà=  jÝ=  j\  jY  jƒ  j€  jë  jè  j  j  j  jŒ  j¶  j³  j  j  j÷  jô  jq%  jn%  j&  j&  jƒ&  j€&  jD'  jA'  j£'  j '  jr(  jo(  j§(  j¤(  jË*  jÈ*  j+  j+  j‰+  j†+  jé1  jæ1  j'5  j$5  jx5  ju5  j6  j6  jx6  ju6  jþ8  jû8  jA9  j>9  j,:  j):  ja<  j^<  j=  j=  j=  jš=  jØ=  jÕ=  uŒ	nametypes”}”(jà=  ‰j\  ‰jƒ  ‰jë  ‰j  ‰j  ‰j¶  ‰j  ‰j÷  ‰jq%  ‰j&  ‰jƒ&  ‰jD'  ‰j£'  ‰jr(  ‰j§(  ‰jË*  ‰j+  ‰j‰+  ‰jé1  ‰j'5  ‰jx5  ‰j6  ‰jx6  ‰jþ8  ‰jA9  ‰j,:  ‰ja<  ‰j=  ‰j=  ‰jØ=  ‰uh}”(jÝ=  h·jY  j  j€  j_  jè  j†  j  jî  jŒ  j  j³  j’  j  j¹  jô  j
  jn%  jú  j&  jt%  j€&  j&  jA'  j†&  j '  jG'  jo(  j¦'  j¤(  ju(  jÈ*  jª(  j+  jÎ*  j†+  j+  jæ1  jŒ+  j$5  jì1  ju5  j*5  j6  j{5  ju6  j6  jû8  j{6  j>9  j9  j):  jD9  j^<  j/:  j=  jd<  jš=  j	=  jÕ=  j =  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”]”(hŒsystem_message”“”)”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjl>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhji>  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œline”MkŒsource”hÊuh1jg>  hj¦'  h²hh³hÊh´Mkubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjˆ>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj…>  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MuŒsource”hÊuh1jg>  hj¦'  h²hh³hÊh´Muubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hj£>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj >  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”M/
Œsource”hÊuh1jg>  hj+  h²hh³hÊh´M/
ubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hj¾>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj»>  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MŒsource”hÊuh1jg>  hjì1  h²hh³hÊh´Mubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjÙ>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhjÖ>  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”M5Œsource”hÊuh1jg>  hjì1  h²hh³hÊh´M5ubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjô>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhjñ>  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MÆŒsource”hÊuh1jg>  hjD9  h²hh³hÊh´MÆubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hj?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj?  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MÌŒsource”hÊuh1jg>  hjD9  h²hh³hÊh´MÌubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hj*?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj'?  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MÜŒsource”hÊuh1jg>  hjD9  h²hh³hÊh´MÜubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjE?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhjB?  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MéŒsource”hÊuh1jg>  hjD9  h²hh³hÊh´Méubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hj`?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj]?  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MŒsource”hÊuh1jg>  hj/:  h²hh³hÊh´Mubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hj{?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhjx?  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”M½Œsource”hÊuh1jg>  hjd<  h²hh³hÊh´M½ubjh>  )”}”(hhh]”hÌ)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hj–?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj“?  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j‚>  Œline”MàŒsource”hÊuh1jg>  hj	=  h²hh³hÊh´MàubeŒtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nh²hub.