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.enable
103    Enable all event tracing within GROUP.
108 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.filter = FILTER
109    Set FILTER rule to the GROUP:EVENT.
111 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.actions = ACTION[, ACTION2[...]]
112    Set ACTIONs to the GROUP:EVENT.
118    group name is "kprobes".
129 ------------------------
131 Since it is too long to write a histogram action as a string for per-event
132 action option, there are tree-style options under per-event 'hist' subkey
136 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]keys = KEY1[, KEY2[...]]
141 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]values = VAL1[, VAL2[...]]
144 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]sort = SORT1[, SORT2[...]]
147 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]size = NR_ENTRIES
150 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]name = NAME
153 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]var.VARIABLE = EXPR
156 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]<pause|continue|clear>
159 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]onmatch.[M.]event = GROUP.EVENT
164 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]onmatch.[M.]trace = EVENT[, ARG1[...]]
169 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]onmax.[M.]var = VAR
172 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]onchange.[M.]var = VAR
175 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]<onmax|onchange>.[M.]save = ARG1[, ARG2[...]]
180 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]<onmax|onchange>.[M.]snapshot
185 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.filter = FILTER_EXPR
188 Note that this 'hist' option can conflict with the per-event 'actions'
195 All boot-time tracing options starting with ``ftrace`` will be enabled at the
199 boot-time tracing.
226                         keys = func.sym, lat
232                 keys = func
236                 keys = func
237                 var.lat = common_timestamp.usecs - $ts0
245 Also, boot-time tracing supports "instance" node, which allows us to run
264 With the trigger action and kprobes, you can trace function-graph while
284 This boot-time tracing also supports ftrace kernel parameters via boot
288 …trace_options=sym-addr trace_event=initcall:* tp_printk trace_buf_size=1M ftrace=function ftrace_f…
293         trace_options = sym-addr