From: Sven Schnelle <svens@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/synthetic: use union instead of casts
Date: Wed, 09 Aug 2023 09:16:47 +0200 [thread overview]
Message-ID: <yt9dr0ocptwg.fsf@linux.ibm.com> (raw)
In-Reply-To: <20230808160547.59e6efd9@gandalf.local.home> (Steven Rostedt's message of "Tue, 8 Aug 2023 16:05:47 -0400")
Steven Rostedt <rostedt@goodmis.org> writes:
> On Tue, 08 Aug 2023 19:33:06 +0200
> Sven Schnelle <svens@linux.ibm.com> wrote:
>
>> Steven Rostedt <rostedt@goodmis.org> writes:
>>
>> > The "dynamic" I was using wasn't about the fields were dynamic (union), but
>> > because the field the offset/len combo represents is of dynamic size. It's
>> > used all over the trace_events code.
>> >
>> > I would have in include/linux/trace_events.h (right above struct trace_entry):
>> >
>> > /* Used to find the offset and length of dynamic fields in trace events */
>> > struct trace_dynamic_info {
>> > #ifdef CONFIG_CPU_BIG_ENDIAN
>> > u16 offset;
>> > u16 len;
>> > #else
>> > u16 len;
>> > u16 offset;
>> > #endif
>> > };
>> >
>> > And then it kernel/trace/trace.h:
>> >
>> > union trace_synthetic_field {
>> > u8 as_u8;
>> > u16 as_u16;
>> > u32 as_u32;
>> > u64 as_u64;
>> > struct trace_dynamic_info as_dynamic;
>> > };
>>
>> Ok.
>>
>> > I could work on the part of the trace_dynamic_info if you want.
>>
>> Whatever you prefer. Should i update my patch and send it again, or do
>> you want to adjust it?
>>
>
> How quickly do you need it. I can hopefully start working on it this week.
I would like to have the bugfix in as soon as possible, as this is
triggering a lot of KASAN warnings in our CI (besides breaking the
synthetic events on our platform). I sent a v2 of my patch, so we
apply that. The rest of the changes are not urgent.
Thanks
Sven
prev parent reply other threads:[~2023-08-09 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 14:21 [PATCH] tracing/synthetic: use union instead of casts Sven Schnelle
2023-08-08 17:27 ` Steven Rostedt
2023-08-08 17:33 ` Sven Schnelle
2023-08-08 20:05 ` Steven Rostedt
2023-08-09 7:16 ` Sven Schnelle [this message]
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=yt9dr0ocptwg.fsf@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.