diff options
| author |  Steven Rostedt (Google) <rostedt@goodmis.org>
| 2023-05-23 23:09:13 -0400 |
|---|---|---|
| committer | Steven Rostedt (Google) <rostedt@goodmis.org>
| 2023-05-23 23:38:23 -0400 |
| commit | 4b512860bdbdddcf41467ebd394f27cb8dfb528c (patch) | |
| tree | c17979b6a45491440824ab0b7ef94416e334a063 /kernel/trace/trace.c | |
| parent | tracing/histograms: Allow variables to have some modifiers (diff) | |
| download | linux-4b512860bdbdddcf41467ebd394f27cb8dfb528c.tar.gz linux-4b512860bdbdddcf41467ebd394f27cb8dfb528c.tar.bz2 linux-4b512860bdbdddcf41467ebd394f27cb8dfb528c.zip | |
tracing: Rename stacktrace field to common_stacktrace
The histogram and synthetic events can use a pseudo event called
"stacktrace" that will create a stacktrace at the time of the event and
use it just like it was a normal field. We have other pseudo events such
as "common_cpu" and "common_timestamp". To stay consistent with that,
convert "stacktrace" to "common_stacktrace". As this was used in older
kernels, to keep backward compatibility, this will act just like
"common_cpu" did with "cpu". That is, "cpu" will be the same as
"common_cpu" unless the event has a "cpu" field. In which case, the
event's field is used. The same is true with "stacktrace".
Also update the documentation to reflect this change.
Link: https://lore.kernel.org/linux-trace-kernel/20230523230913.6860e28d@rorschach.local.home
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Tom Zanussi <zanussi@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace.c')
| -rw-r--r-- | kernel/trace/trace.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c index ebc59781456a..81801dc31784 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -5752,7 +5752,7 @@ static const char readme_msg[] = "\t table using the key(s) and value(s) named, and the value of a\n" "\t sum called 'hitcount' is incremented. Keys and values\n" "\t correspond to fields in the event's format description. Keys\n" - "\t can be any field, or the special string 'stacktrace'.\n" + "\t can be any field, or the special string 'common_stacktrace'.\n" "\t Compound keys consisting of up to two fields can be specified\n" "\t by the 'keys' keyword. Values must correspond to numeric\n" "\t fields. Sort keys consisting of up to two fields can be\n" |