From: Sven Schnelle <svens@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH RESEND v3 0/3] few fixes for synthetic trace events
Date: Wed, 16 Aug 2023 17:49:25 +0200 [thread overview]
Message-ID: <20230816154928.4171614-1-svens@linux.ibm.com> (raw)
Hi Steven,
I'm now sending these patches in one patchset, because the second patch
has a dependeny on the union vs. cast fix.
Changes in v3:
- remove superfluous struct around union trace_synth_field
Changes in v2:
- cosmetic changes
- add struct trace_dynamic_info to include/linux/trace_events.h
Sven Schnelle (3):
tracing/synthetic: use union instead of casts
tracing/synthetic: skip first entry for stack traces
tracing/synthetic: allocate one additional element for size
include/linux/trace_events.h | 11 ++++
kernel/trace/trace.h | 8 +++
kernel/trace/trace_events_synth.c | 103 ++++++++++++------------------
3 files changed, 60 insertions(+), 62 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-16 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 15:49 Sven Schnelle [this message]
2023-08-16 15:49 ` [PATCH RESEND v3 1/3] tracing/synthetic: use union instead of casts Sven Schnelle
2023-08-25 8:26 ` kernel test robot
2023-08-16 15:49 ` [PATCH RESEND v3 2/3] tracing/synthetic: skip first entry for stack traces Sven Schnelle
2023-08-16 15:49 ` [PATCH RESEND v3 3/3] tracing/synthetic: allocate one additional element for size Sven Schnelle
2023-08-17 15:05 ` [PATCH RESEND v3 0/3] few fixes for synthetic trace events Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230816154928.4171614-1-svens@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).