From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Li Zefan <lizf@cn.fujitsu.com>, Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [PATCH 0/6] [GIT PULL] tracing: automate output for ftrace formats
Date: Sun, 13 Sep 2009 16:59:31 +0200 [thread overview]
Message-ID: <20090913145931.GA24187@elte.hu> (raw)
In-Reply-To: <20090913034302.134417216@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> Ingo,
>
> Currently, the output for the format files for the internal ftrace
> plugin entries is done by hand. This becomes difficult to maintain
> and error prone. If a change happens to a structure, it is likely
> that it will not be shown in the format file which binary readers
> of ftrace require.
>
> This patch series implements the logic that is used by TRACE_EVENT
> to use macros that create the structures and those same macros also
> show the output layout in the format files. This guarantees that the
> structures and the output formats remain in-sync.
>
> Again, this is based off of tip/tracing/core2
>
> Please pull the latest tip/tracing/core3 tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core3
Pulled, thanks a lot Steve!
Ingo
prev parent reply other threads:[~2009-09-13 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 3:43 [PATCH 0/6] [GIT PULL] tracing: automate output for ftrace formats Steven Rostedt
2009-09-13 3:43 ` [PATCH 1/6] tracing: allow filter predicates to handle ksym symbols Steven Rostedt
2009-09-13 3:43 ` [PATCH 2/6] tracing: use macros to create internal ftrace entry ring buffer structures Steven Rostedt
2009-09-13 3:43 ` [PATCH 3/6] tracing: show details of structures within the ftrace structures Steven Rostedt
2009-09-13 3:43 ` [PATCH 4/6] tracing: use the new trace_entries.h to create format files Steven Rostedt
2009-09-13 3:43 ` [PATCH 5/6] tracing: remove trace_event_types.h Steven Rostedt
2009-09-13 3:43 ` [PATCH 6/6] tracing: add filter event logic to special, mmiotrace and boot tracers Steven Rostedt
2009-09-13 14:59 ` Ingo Molnar [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=20090913145931.GA24187@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
/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