Lines Matching +full:event +full:-
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.
66 (you can enable it by the "traceon" event trigger action)
79 Set CPUMASK as trace cpu-mask.
81 ftrace.[instance.INSTANCE.]events = EVENT[, EVENT2[...]]
82 Enable given events on boot. You can use a wild card in EVENT.
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.
105 ftrace.[instance.INSTANCE.]event.enable
106 Enable all event tracing.
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.
114 ftrace.[instance.INSTANCE.]event.kprobes.EVENT.probes = PROBE[, PROBE2[...]]
115 Defines new kprobe event based on PROBEs. It is able to define
116 multiple probes on one event, but those must have same type of
117 arguments. This option is available only for the event which
120 ftrace.[instance.INSTANCE.]event.synthetic.EVENT.fields = FIELD[, FIELD2[...]]
121 Defines new synthetic event with FIELDs. Each field should be
124 Note that kprobe and synthetic event definitions can be written under
126 take care for event name conflict.
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
134 please read the event histogram document (Documentation/trace/histogram.rst)
136 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]keys = KEY1[, KEY2[...]]
139 if there is one histogram on the event.
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
160 Set histogram 'onmatch' handler matching event parameter.
164 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.hist.[N.]onmatch.[M.]trace = EVENT[, ARG1[...]]
166 EVENT must be a synthetic event name, and ARG1... are parameters
167 for that event. Mandatory if 'onmatch.event' option is set.
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.
209 For example, to add filter and actions for each event, define kprobe
213 ftrace.event {
237 var.lat = common_timestamp.usecs - $ts0
239 event = initcall.initcall_start
245 Also, boot-time tracing supports "instance" node, which allows us to run
261 The instance node also accepts event nodes so that each instance
262 can customize its event tracing.
264 With the trigger action and kprobes, you can trace function-graph while
271 event.kprobes {
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