Lines Matching +full:keys +full:- +full:per +full:- +full:group
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,
27 .. [1] See :ref:`Documentation/admin-guide/bootconfig.rst <bootconfig>`
28 .. [2] See :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>`
31 ---------------------
37 Output trace-event data on printk buffer too.
53 Add fgraph non-tracing function filters.
56 Ftrace Per-instance Options
57 ---------------------------
65 Enable/Disable tracing on this instance when starting boot-time tracing.
79 Set CPUMASK as trace cpu-mask.
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
100 Enable GROUP:EVENT tracing.
102 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.filter = FILTER
103 Set FILTER rule to the GROUP:EVENT.
105 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.actions = ACTION[, ACTION2[...]]
106 Set ACTIONs to the GROUP:EVENT.
112 group name is "kprobes".
126 All boot-time tracing options starting with ``ftrace`` will be enabled at the
130 boot-time tracing.
156 actions = "hist:keys=func.sym,lat:vals=lat:sort=lat"
159 actions = "hist:keys=func:ts0=common_timestamp.usecs"
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
185 With the trigger action and kprobes, you can trace function-graph while
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