From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Jens Axboe" <jens.axboe@oracle.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH tip 2/2] tracing: Introduce trace_buffer_{lock_reserve,unlock_commit}
Date: Fri, 6 Feb 2009 01:02:52 +0100 [thread overview]
Message-ID: <20090206000252.GC16040@elte.hu> (raw)
In-Reply-To: <20090205181413.GI17653@ghostprotocols.net>
* Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> Impact: new API
>
> These new functions do what previously was being open coded, reducing
> the number of details ftrace plugin writers have to worry about.
>
> It also standardizes the handling of stacktrace, userstacktrace and
> other trace options we may introduce in the future.
>
> With this patch, for instance, the blk tracer (and some others already
> in the tree) can use the "userstacktrace" /d/tracing/trace_options
> facility.
>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Frédéric Weisbecker <fweisbec@gmail.com>
> Cc: Jens Axboe <jens.axboe@oracle.com>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> ---
> block/blktrace.c | 21 ++------
> kernel/trace/kmemtrace.c | 19 ++-----
> kernel/trace/trace.c | 94 +++++++++++++++++++++----------------
> kernel/trace/trace.h | 11 ++++
> kernel/trace/trace_boot.c | 20 ++------
> kernel/trace/trace_branch.c | 7 +--
> kernel/trace/trace_hw_branches.c | 7 +--
> kernel/trace/trace_mmiotrace.c | 20 +++-----
> kernel/trace/trace_power.c | 20 ++------
> 9 files changed, 102 insertions(+), 117 deletions(-)
Applied to tip:tracing/ftrace, thanks!
Ingo
prev parent reply other threads:[~2009-02-06 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 18:14 [PATCH tip 2/2] tracing: Introduce trace_buffer_{lock_reserve,unlock_commit} Arnaldo Carvalho de Melo
2009-02-05 22:58 ` Frederic Weisbecker
2009-02-06 1:54 ` Arnaldo Carvalho de Melo
2009-02-06 2:39 ` Frederic Weisbecker
2009-02-06 3:10 ` Arnaldo Carvalho de Melo
2009-02-08 13:04 ` Frederic Weisbecker
2009-02-08 15:17 ` Steven Rostedt
2009-02-06 0:02 ` 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=20090206000252.GC16040@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox