From: Filipe Brandenburger <filbranden@google.com>
To: Steven Rostedt <rostedt@goodmis.org>, Li Zefan <lizefan@huawei.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Filipe Brandenburger <filbranden@google.com>
Subject: [PATCH 0/3] tracing: fix macro expansion and refactor some of dynamic_array support
Date: Fri, 28 Feb 2014 21:32:15 -0800 [thread overview]
Message-ID: <1393651938-16418-1-git-send-email-filbranden@google.com> (raw)
Hi Steven Rostedt, Li Zefan,
This fixes an issue with macro expansion introduced in commit 7d536cb3f
(tracing/events: record the size of dynamic arrays).
I split it in 3 patches, the first fixes a bug, the second improves the code to
evaluate the expression only once and the third refactors an u32 holding two
pieces of data in lower/higher 16 bits into a struct to make the code cleaner.
I split them this way since I expect the first two to be more straightforward
while the third one might generate some discussion. I'd be happy to squash them
into a single one if you'd prefer that.
Cheers,
Filipe
Filipe Brandenburger (3):
tracing: correctly expand len expressions from __dynamic_array macro
tracing: evaluate len expression only once in __dynamic_array macro
tracing: introduce a trace_data_offset struct to store array size
include/linux/ftrace_event.h | 5 +++++
include/trace/ftrace.h | 26 ++++++++++++++------------
kernel/trace/trace_events_filter.c | 13 ++++++++++---
3 files changed, 29 insertions(+), 15 deletions(-)
--
1.9.0.279.gdc9e3eb
next reply other threads:[~2014-03-01 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 5:32 Filipe Brandenburger [this message]
2014-03-01 5:32 ` [PATCH 1/3] tracing: correctly expand len expressions from __dynamic_array macro Filipe Brandenburger
2014-03-03 19:51 ` Steven Rostedt
2014-03-03 19:57 ` Filipe Brandenburger
2014-03-01 5:32 ` [PATCH 2/3] tracing: evaluate len expression only once in " Filipe Brandenburger
2014-03-01 5:32 ` [PATCH 3/3] tracing: introduce a trace_data_offset struct to store array size Filipe Brandenburger
2014-03-03 20:48 ` Steven Rostedt
2014-03-03 20:59 ` 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=1393651938-16418-1-git-send-email-filbranden@google.com \
--to=filbranden@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®