From: Steven Rostedt <rostedt@goodmis.org>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] tracing/mm: don't trace kfree on offline CPUs
Date: Tue, 16 Feb 2016 10:01:21 -0500 [thread overview]
Message-ID: <20160216100121.6ef2145d@gandalf.local.home> (raw)
In-Reply-To: <CAOJe8K1G3n8Mfi=421og9wOnyq2n-45x69JpQe80-D2xzRE95Q@mail.gmail.com>
On Tue, 16 Feb 2016 08:52:24 +0300
Denis Kirjanov <kda@linux-powerpc.org> wrote:
> On 2/15/16, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Sun, 14 Feb 2016 23:19:42 +0300
> > Denis Kirjanov <kda@linux-powerpc.org> wrote:
> >
> >
> >> >> TP_PROTO(unsigned long call_site, const void *ptr),
> >> >>
> >> >> - TP_ARGS(call_site, ptr)
> >> >> + TP_ARGS(call_site, ptr),
> >> >> +
> >> >> + /*
> >> >> + * This trace can be potentially called from an offlined cpu.
> >> >> + * Since trace points use RCU and RCU should not be used from
> >> >> + * offline cpus, filter such calls out.
> >> >> + * While this trace can be called from a preemptable section,
> >> >> + * it has no impact on the condition since tasks can migrate
> >> >> + * only from online cpus to other online cpus. Thus its safe
> >> >> + * to use raw_smp_processor_id.
> >> >> + */
> >> >> + TP_CONDITION(cpu_online(raw_smp_processor_id()))
> >> >
> >> > This is starting to become a common occurrence. Perhaps it is best to
> >> > just hardcode this into the tracepoint code itself?
> >>
> >> Can you take it as a fix for now. I'll post the follow-up patch then
> >> for rcu and offline cpus
> >> issue.
> >
> > Actually, I prefer not to add more checks for cpu_online(), if its
> > going to become the default.
> >
> > Does this work for you instead?
>
> Hm, somehow it doesn't work:
But your patch works? Strange, because my exit condition is done before
the conditional part of the trace event. Thus, if this didn't work,
than your original patch should not work either.
-- Steve
next prev parent reply other threads:[~2016-02-16 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 18:22 Denis Kirjanov
2016-02-13 18:22 ` [PATCH 2/2] tracing/rcu: don't trace rcu_callback " Denis Kirjanov
2016-02-13 19:25 ` kbuild test robot
2016-02-14 16:43 ` Steven Rostedt
2016-02-14 17:35 ` Denis Kirjanov
2016-02-14 16:45 ` [PATCH 1/2] tracing/mm: don't trace kfree " Steven Rostedt
2016-02-14 17:35 ` Denis Kirjanov
2016-02-14 20:19 ` Denis Kirjanov
2016-02-15 17:32 ` Steven Rostedt
2016-02-16 5:52 ` Denis Kirjanov
2016-02-16 11:03 ` Paul E. McKenney
2016-02-16 15:01 ` Steven Rostedt [this message]
2016-02-16 15:03 ` 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=20160216100121.6ef2145d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kda@linux-powerpc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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
all inboxes | Powered by JetHome®