From: Eric Dumazet <eric.dumazet@gmail.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jason Baron <jbaron@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: [PATCH] Tracepoint: introduce tracepoint() API
Date: Fri, 25 Nov 2011 23:43:25 +0100 [thread overview]
Message-ID: <1322261005.2550.6.camel@edumazet-laptop> (raw)
In-Reply-To: <20111125221411.GA11733@Krystal>
Le vendredi 25 novembre 2011 à 17:14 -0500, Mathieu Desnoyers a écrit :
> Introduce:
>
> tracepoint(event_name, arg1, arg2, ...)
>
> while keeping the old tracepoint API in place, e.g.:
>
> trace_event_name(arg1, arg2, ...)
>
> This allows skipping parameter side-effects (pointer dereference,
> function calls, ...) when the tracepoint is not dynamically activated.
>
> This allows progressive (and partial) API transition from trace_*(...)
> to tracepoint(*, ...). This differs from the previous attempt to
> introduce this change by Jason Baron in that it supports both the
> original and new tracepoint APIs, which makes the transition smoother
> than having to change all instrumentation at once.
>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Acked-by: Jason Baron <jbaron@redhat.com>
> Link: https://lkml.org/lkml/2009/5/19/328
> CC: Eric Dumazet <eric.dumazet@gmail.com>
> CC: Peter Zijlstra <peterz@infradead.org>
> CC: Ingo Molnar <mingo@elte.hu>
> CC: Christoph Lameter <cl@linux-foundation.org>
> ---
Seems good to me, thanks Mathieu !
Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
prev parent reply other threads:[~2011-11-25 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 22:14 Mathieu Desnoyers
2011-11-25 22:43 ` Eric Dumazet [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=1322261005.2550.6.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=cl@linux-foundation.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®