From: Steven Rostedt <rostedt@goodmis.org>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing: introduce TRACE_EVENT_FN_COND macro
Date: Mon, 7 Dec 2015 09:57:58 -0500 [thread overview]
Message-ID: <20151207095758.028cdae4@gandalf.local.home> (raw)
In-Reply-To: <CAOJe8K3wP_KT9XAOhduw35dD=QVaDUVBMi-jSeRDLGD+Zs-a-A@mail.gmail.com>
On Mon, 7 Dec 2015 17:42:42 +0300
Denis Kirjanov <kda@linux-powerpc.org> wrote:
> On 11/24/15, Denis Kirjanov <kda@linux-powerpc.org> wrote:
> > TRACE_EVENT_FN can't be used in some circumstances
> > like invoking trace functions from offlined CPU due
> > to RCU usage.
> >
> > This patch adds the TRACE_EVENT_FN_COND macro
> > to make such trace points conditional.
> >
> > Signed-off-by: Denis Kirjanov <kda@linux-powerpc.org>
>
> Hi Steven,
> are you going to take this series through your tree?
>
Yeah, thanks for the reminder!
-- Steve
next prev parent reply other threads:[~2015-12-07 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 18:23 [PATCH 1/2] tracing: introduce TRACE_EVENT_FN_COND macro Denis Kirjanov
2015-11-24 18:23 ` [PATCH 2/2] powerpc: tracing: don't trace hcalls on offline CPUs Denis Kirjanov
2015-11-26 6:39 ` Michael Ellerman
2015-11-26 8:15 ` Denis Kirjanov
2015-11-26 9:26 ` Michael Ellerman
2015-11-26 20:10 ` Denis Kirjanov
2015-12-07 20:52 ` Steven Rostedt
2015-12-07 21:02 ` Benjamin Herrenschmidt
2015-12-07 21:33 ` Steven Rostedt
2015-12-14 10:00 ` Michael Ellerman
2015-12-14 10:05 ` Denis Kirjanov
2015-12-07 14:42 ` [PATCH 1/2] tracing: introduce TRACE_EVENT_FN_COND macro Denis Kirjanov
2015-12-07 14:57 ` Steven Rostedt [this message]
2015-12-11 19:40 ` 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=20151207095758.028cdae4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kda@linux-powerpc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).