Lines Matching refs:kernel
135 of the kernel can use them to generate or add hooks to them.
174 Enable the kernel tracing infrastructure.
184 kernel cmdline at boot time for debugging (tracing) driver
197 Enable the kernel to trace every kernel function. This is done
199 instruction at the beginning of every kernel function, which NOP
213 Enable the kernel to trace a function at both its return
230 can function trace, and this table is linked into the kernel
235 See the files in /sys/kernel/debug/tracing:
240 This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but
266 This option enables kernel function probe (fprobe) based on ftrace.
267 The fprobe is similar to kprobes, but probes only for kernel function
278 This option enables the kernel function profiler. A file is created
295 kernel and displays it in /sys/kernel/debug/tracing/stack_trace.
298 kernel executes, and keeping a maximum stack depth value and
304 on the kernel command line.
307 sysctl kernel.stack_tracer_enabled
335 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency
337 (Note that kernel size and overhead increase with this option
359 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency
361 (Note that kernel size and overhead increase with this option
380 This tracer, when enabled will create one or more kernel threads,
383 something other than the kernel. For example, if a
395 A kernel thread is created that will spin with interrupts disabled
451 The timerlat tracer aims to help the preemptive kernel developers
454 The tracer creates a per-cpu kernel thread with real-time priority.
492 This tracer hooks to various trace points in the kernel,
511 echo 1 > /sys/kernel/debug/tracing/snapshot
523 echo 1 > /sys/kernel/debug/tracing/per_cpu/cpu2/snapshot
550 kernel. This profiler will also enable the likely/unlikely
568 in the kernel. It will display the results in:
570 /sys/kernel/debug/tracing/trace_stat/branch_annotated
580 taken in the kernel is recorded whether it hit or miss.
583 /sys/kernel/debug/tracing/trace_stat/branch_all
606 calls in the kernel. The difference between this and the
629 git://git.kernel.dk/blktrace.git
634 echo blk > /sys/kernel/debug/tracing/current_tracer
635 cat /sys/kernel/debug/tracing/trace_pipe
669 recursion or any unexpected execution path which leads to a kernel
770 by way of an in-kernel API.
784 can be used like an existing kernel trace event. User trace
827 When the tracepoint is enabled, it kicks off a kernel thread that
878 To fix this, there's a special macro in the kernel that can be used
883 used to show what enums/sizeof the kernel tried to convert.
893 increase the memory footprint of the running kernel.
945 Note that on a kernel compiled with this config, ftrace will
977 with the event enabled. This adds a bit more time for kernel boot
1002 kernel boot sequence, the test will start that kicks off
1070 tristate "Test module for in-kernel synthetic event generation"
1074 functionality of in-kernel synthetic event definition and
1083 tristate "Test module for in-kernel kprobe event generation"
1087 functionality of in-kernel kprobe event definition.
1117 source "kernel/trace/rv/Kconfig"