Searched refs:tracers (Results 1 – 9 of 9) sorted by relevance
| /linux/tools/tracing/latency/ |
| H A D | latency-collector.c | 927 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/Documentation/core-api/real-time/ |
| H A D | kernel-configuration.rst | 201 latency problems arise. Nonetheless, some tracers do incur latency overhead 206 Users should *not* make use of tracers or trace events during production 216 These tracers do incur measurable latency overhead even when tracing is not
|
| /linux/kernel/trace/ |
| H A D | Kconfig | 173 # enabled by all tracers (context switch and event tracer) they select TRACING. 628 Note, the latency tracers select this option. To disable it, 629 all the latency tracers need to be disabled. 649 or irq latency tracers are enabled, as those need to swap as well 712 Selected by tracers that will trace the likely and unlikely 713 conditions. This prevents the tracers themselves from being 920 to be shared between multiple tracers. It isn't meant to be 922 selected by tracers that use it. 1136 tracers of ftrace. 1262 tristate "Test module to create a preempt / IRQ disable delay thread to test latency tracers" [all …]
|
| H A D | trace.c | 96 struct tracers { struct 1437 struct tracers *t, *n; in free_tracers() 1441 list_for_each_entry_safe(t, n, &tr->tracers, list) { in free_tracers() 5007 struct tracers *t; in tracing_set_tracer() 5022 list_for_each_entry(t, &tr->tracers, list) { in tracing_set_tracer() 8045 struct tracers *t; in get_global_flags_val() 8047 list_for_each_entry(t, &global_trace.tracers, list) { in get_global_flags_val() 8057 static int add_tracer_options(struct trace_array *tr, struct tracers *t) in add_tracer_options() 8075 struct tracers *t; in add_tracer() 8095 list_add(&t->list, &tr->tracers); in add_tracer() [all …]
|
| H A D | trace.h | 424 struct list_head tracers; member
|
| /linux/tools/testing/selftests/ftrace/test.d/ |
| H A D | functions | 143 check_requires() { # Check required files and tracers
|
| /linux/arch/arm/kernel/ |
| H A D | entry-common.S | 93 str scno, [tsk, #TI_ABI_SYSCALL] @ make sure tracers see update
|
| /linux/Documentation/trace/ |
| H A D | boottime-trace.rst | 258 several tracers for different purpose at once. For example, one tracer
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 983 or one. NMIs, irqs, and tracers are counted by the
|