summaryrefslogtreecommitdiff
path: root/kernel/trace/tracing_map.c
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@linux.intel.com>2018-01-16 05:51:45 +0300
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2018-03-11 00:05:52 +0300
commitad42febe51ae0a2e875f507a37a6329277f75fdd (patch)
tree680db1206c9a42419b70e9f45d2865fe1f008a70 /kernel/trace/tracing_map.c
parent9b1ae035c9304ed1e183de3b3bb08eafd01a7553 (diff)
downloadlinux-ad42febe51ae0a2e875f507a37a6329277f75fdd.tar.xz
tracing: Add hist trigger timestamp support
Add support for a timestamp event field. This is actually a 'pseudo-' event field in that it behaves like it's part of the event record, but is really part of the corresponding ring buffer event. To make use of the timestamp field, users can specify "common_timestamp" as a field name for any histogram. Note that this doesn't make much sense on its own either as either a key or value, but needs to be supported even so, since follow-on patches will add support for making use of this field in time deltas. The common_timestamp 'field' is not a bona fide event field - so you won't find it in the event description - but rather it's a synthetic field that can be used like a real field. Note that the use of this field requires the ring buffer be put into 'absolute timestamp' mode, which saves the complete timestamp for each event rather than an offset. This mode will be enabled if and only if a histogram makes use of the "common_timestamp" field. Link: http://lkml.kernel.org/r/97afbd646ed146e26271f3458b4b33e16d7817c2.1516069914.git.tom.zanussi@linux.intel.com Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Baohong Liu <baohong.liu@intel.com> [kasan use-after-free fix] Signed-off-by: Vedang Patel <vedang.patel@intel.com> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/tracing_map.c')
0 files changed, 0 insertions, 0 deletions