diff options
author | Steven Rostedt (Google) <rostedt@goodmis.org> | 2023-05-24 06:09:13 +0300 |
---|---|---|
committer | Steven Rostedt (Google) <rostedt@goodmis.org> | 2023-05-24 06:38:23 +0300 |
commit | 4b512860bdbdddcf41467ebd394f27cb8dfb528c (patch) | |
tree | c17979b6a45491440824ab0b7ef94416e334a063 /scripts/gcc-x86_32-has-stack-protector.sh | |
parent | e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c (diff) | |
download | linux-4b512860bdbdddcf41467ebd394f27cb8dfb528c.tar.xz |
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 'scripts/gcc-x86_32-has-stack-protector.sh')
0 files changed, 0 insertions, 0 deletions