Home
last modified time | relevance | path

Searched refs:tracers (Results 1 – 7 of 7) sorted by relevance

/linux-6.3-rc2/tools/tracing/latency/
A Dlatency-collector.c927 char **tracers; in show_available() local
932 for (i = 0; tracers && tracers[i]; i++) { in show_available()
937 if (!tracers) { in show_available()
944 tracefs_list_free(tracers); in show_available()
949 for (i = 0; tracers[i]; i++) { in show_available()
951 printf("%s\n", tracers[i]); in show_available()
953 tracefs_list_free(tracers); in show_available()
958 char **tracers; in tracer_valid() local
964 if (!tracers) { in tracer_valid()
968 for (i = 0; tracers[i]; i++) in tracer_valid()
[all …]
/linux-6.3-rc2/kernel/trace/
A DKconfig148 # enabled by all tracers (context switch and event tracer) they select TRACING.
546 or irq latency tracers are enabled, as those need to swap as well
609 Selected by tracers that will trace the likely and unlikely
610 conditions. This prevents the tracers themselves from being
770 to be shared between multiple tracers. It isn't meant to be
772 selected by tracers that use it.
973 tracers of ftrace.
1065 tristate "Test module to create a preempt / IRQ disable delay thread to test latency tracers"
1069 tracers by executing a preempt or irq disable section with a user
/linux-6.3-rc2/Documentation/trace/
A Dftrace.rst103 This holds the different types of tracers that
105 tracers listed here can be configured by
166 Some of the tracers record the max latency.
178 Some latency tracers will record a trace whenever the
620 Certain tracers may change the timestamp mode used when
813 tracers from tracing simply echo "nop" into
1234 The latency tracers will enable function tracing
1236 it is disabled, the latency tracers do not trace
1307 Unlike other tracers, the process' command line
1716 tracers.
[all …]
A Dboottime-trace.rst246 several tracers for different purpose at once. For example, one tracer
/linux-6.3-rc2/tools/testing/selftests/ftrace/test.d/
A Dfunctions143 check_requires() { # Check required files and tracers
/linux-6.3-rc2/Documentation/trace/coresight/
A Dcoresight.rst453 Coresight tracers are represented using the Perf framework's Performance
467 Regardless of the number of tracers available in a system (usually equal to the
631 Using the System Trace Macrocell module is the same as the tracers - the only
/linux-6.3-rc2/Documentation/RCU/Design/Data-Structures/
A DData-Structures.rst950 or one. NMIs, irqs, and tracers are counted by the

Completed in 26 milliseconds