Home
last modified time | relevance | path

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

/linux-5.19.10/tools/tracing/latency/
Dlatency-collector.c927 char **tracers; in show_available() local
931 tracers = tracefs_tracers(NULL); in show_available()
932 for (i = 0; tracers && tracers[i]; i++) { in show_available()
933 if (is_relevant_tracer(tracers[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()
950 if (is_relevant_tracer(tracers[i])) in show_available()
951 printf("%s\n", tracers[i]); in show_available()
953 tracefs_list_free(tracers); in show_available()
[all …]
/linux-5.19.10/kernel/trace/
DKconfig132 # enabled by all tracers (context switch and event tracer) they select TRACING.
524 or irq latency tracers are enabled, as those need to swap as well
587 Selected by tracers that will trace the likely and unlikely
588 conditions. This prevents the tracers themselves from being
748 to be shared between multiple tracers. It isn't meant to be
750 selected by tracers that use it.
951 tracers of ftrace.
1043 tristate "Test module to create a preempt / IRQ disable delay thread to test latency tracers"
1047 tracers by executing a preempt or irq disable section with a user
/linux-5.19.10/Documentation/trace/
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
233 This influences the tracers "function" and "function_graph"
620 Certain tracers may change the timestamp mode used when
731 Here is the list of current tracers that may be configured.
813 tracers from tracing simply echo "nop" into
851 Here are typical examples of using the tracers when controlling
901 tracers is set, the trace file gives somewhat more information to see
[all …]
Dboottime-trace.rst246 several tracers for different purpose at once. For example, one tracer
/linux-5.19.10/tools/testing/selftests/ftrace/test.d/
Dfunctions143 check_requires() { # Check required files and tracers
/linux-5.19.10/Documentation/trace/coresight/
Dcoresight.rst451 Coresight tracers are represented using the Perf framework's Performance
465 Regardless of the number of tracers available in a system (usually equal to the
585 Using the System Trace Macrocell module is the same as the tracers - the only
/linux-5.19.10/Documentation/RCU/Design/Data-Structures/
DData-Structures.rst950 or one. NMIs, irqs, and tracers are counted by the