Lines Matching +full:ftrace +full:- +full:size
1 .. SPDX-License-Identifier: GPL-2.0
4 Boot-time tracing
12 Boot-time tracing allows users to trace boot-time process including
13 device initialization with full features of ftrace including per-event
14 filter and actions, histograms, kprobe-events and synthetic-events,
23 boot config file [1]_. All options are under "ftrace." or "kernel."
27 .. [1] See :ref:`Documentation/admin-guide/bootconfig.rst <bootconfig>`
28 .. [2] See :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>`
30 Ftrace Global Options
31 ---------------------
33 Ftrace global options have "kernel." prefix in boot config, which means
37 Output trace-event data on printk buffer too.
40 Dump ftrace on Oops. If MODE = 1 or omitted, dump trace buffer
53 Add fgraph non-tracing function filters.
56 Ftrace Per-instance Options
57 ---------------------------
59 These options can be used for each instance including global ftrace node.
61 ftrace.[instance.INSTANCE.]options = OPT1[, OPT2[...]]
62 Enable given ftrace options.
64 ftrace.[instance.INSTANCE.]tracing_on = 0|1
65 Enable/Disable tracing on this instance when starting boot-time tracing.
68 ftrace.[instance.INSTANCE.]trace_clock = CLOCK
69 Set given CLOCK to ftrace's trace_clock.
71 ftrace.[instance.INSTANCE.]buffer_size = SIZE
72 Configure ftrace buffer size to SIZE. You can use "KB" or "MB"
73 for that SIZE.
75 ftrace.[instance.INSTANCE.]alloc_snapshot
78 ftrace.[instance.INSTANCE.]cpumask = CPUMASK
79 Set CPUMASK as trace cpu-mask.
81 ftrace.[instance.INSTANCE.]events = EVENT[, EVENT2[...]]
84 ftrace.[instance.INSTANCE.]tracer = TRACER
87 ftrace.[instance.INSTANCE.]ftrace.filters
90 ftrace.[instance.INSTANCE.]ftrace.notraces
91 This will take an array of NON-tracing function filter rules.
94 Ftrace Per-Event Options
95 ------------------------
97 These options are setting per-event options.
99 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.enable
102 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.filter = FILTER
105 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.actions = ACTION[, ACTION2[...]]
108 ftrace.[instance.INSTANCE.]event.kprobes.EVENT.probes = PROBE[, PROBE2[...]]
114 ftrace.[instance.INSTANCE.]event.synthetic.EVENT.fields = FIELD[, FIELD2[...]]
126 All boot-time tracing options starting with ``ftrace`` will be enabled at the
130 boot-time tracing.
133 processing (for example,. ``kernel.ftrace=function`` and ``kernel.trace_event``
144 ftrace.event {
162 …actions = "hist:keys=func:lat=common_timestamp.usecs-$ts0:onmatch(initcall.initcall_start).initcal…
166 Also, boot-time tracing supports "instance" node, which allows us to run
171 ftrace.instance {
174 ftrace.filters = "user_*"
178 ftrace.filters = "kernel_*"
185 With the trigger action and kprobes, you can trace function-graph while
189 ftrace {
205 This boot-time tracing also supports ftrace kernel parameters via boot
209 …trace_options=sym-addr trace_event=initcall:* tp_printk trace_buf_size=1M ftrace=function ftrace_f…
214 trace_options = sym-addr
218 ftrace = function
222 Note that parameters start with "kernel" prefix instead of "ftrace".