From: Sudeep Holla <sudeep.holla@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH -next] tracepoint: ipi: don't trace IPI on offline CPUs
Date: Wed, 9 Mar 2016 16:40:16 +0000 [thread overview]
Message-ID: <56E051F0.9030800@arm.com> (raw)
In-Reply-To: <20160309110539.603293db@gandalf.local.home>
On 09/03/16 16:05, Steven Rostedt wrote:
> On Wed, 9 Mar 2016 12:22:22 +0000
> Sudeep Holla <sudeep.holla@arm.com> wrote:
>
>
>> Hi Steven,
>>
>> I observed that in "include/linux/tracepoint.h", we have
>> #define __DO_TRACE(tp, proto, args, cond, prercu, postrcu)
>> ...
>> if (!cpu_online(raw_smp_processor_id()))
>> return;
>>
>> if (!(cond))
>> return;
>> ...
>>
>> where !cond check seems reduntant if it's cpu_online check.
>> So, does this patch handle the warning correctly or is there any better
>> way ? I did see few traces with same condition, just thought of checking
>> with you.
>>
>
> Bah, I forgot that we have lockdep checks for when the event isn't
> enabled.
Yes I was about to ask you the same. I did further digging to check if I
was missing something after seeing your series[1] especially patch 2/12
(tracing: Remove duplicate checks for online CPUs)
> Can you try this patch:
It works. Thanks for the quick fix.
Tested-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
[1] http://www.spinics.net/lists/kernel/msg2208604.html
next prev parent reply other threads:[~2016-03-09 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 12:22 [PATCH -next] tracepoint: ipi: don't trace IPI on offline CPUs Sudeep Holla
2016-03-09 16:05 ` Steven Rostedt
2016-03-09 16:40 ` Sudeep Holla [this message]
2016-03-09 16:44 ` 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=56E051F0.9030800@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.