39a39d5b6b
The current trace documentation, the section describing histogram's "onmatch" is not straightforward enough about how this action is applied. It is not clear what criteria are used to "match" both events. A short note is added, describing what exactly is compared in order to match the events. Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Reviewed-by: Tom Zanussi <tom.zanussi@linux.intel.com> [jc: fixed trivial conflict with docs-next] Signed-off-by: Jonathan Corbet <corbet@lwn.net> |
||
---|---|---|
.. | ||
postprocess | ||
coresight-cpu-debug.txt | ||
coresight.txt | ||
events-kmem.rst | ||
events-msr.rst | ||
events-nmi.rst | ||
events-power.rst | ||
events.rst | ||
ftrace-design.rst | ||
ftrace-uses.rst | ||
ftrace.rst | ||
function-graph-fold.vim | ||
histogram.rst | ||
hwlat_detector.rst | ||
index.rst | ||
intel_th.rst | ||
kprobetrace.rst | ||
mmiotrace.rst | ||
ring-buffer-design.txt | ||
stm.rst | ||
sys-t.rst | ||
tracepoint-analysis.rst | ||
tracepoints.rst | ||
uprobetracer.rst |