Lines Matching full:event

13 device initialization with full features of ftrace including per-event
37    Output trace-event data on printk buffer too.
66    (you can enable it by the "traceon" event trigger action)
81 ftrace.[instance.INSTANCE.]events = EVENT[, EVENT2[...]]
82    Enable given events on boot. You can use a wild card in EVENT.
94 Ftrace Per-Event Options
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.
108 ftrace.[instance.INSTANCE.]event.kprobes.EVENT.probes = PROBE[, PROBE2[...]]
109    Defines new kprobe event based on PROBEs. It is able to define
110    multiple probes on one event, but those must have same type of
111    arguments. This option is available only for the event which
114 ftrace.[instance.INSTANCE.]event.synthetic.EVENT.fields = FIELD[, FIELD2[...]]
115    Defines new synthetic event with FIELDs. Each field should be
118 Note that kprobe and synthetic event definitions can be written under
120 take care for event name conflict.
140 For example, to add filter and actions for each event, define kprobe
144   ftrace.event {
182 The instance node also accepts event nodes so that each instance
183 can customize its event tracing.
192         event.kprobes {