From: Scott Wood <scottwood@freescale.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Michael Neuling <mikey@neuling.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
<linuxppc-dev@ozlabs.org>
Subject: Re: question on FSL_EMB perf
Date: Wed, 10 Jun 2015 15:13:56 -0500 [thread overview]
Message-ID: <1433967236.2477.146.camel@freescale.com> (raw)
In-Reply-To: <1433964454.1495.58.camel@twins>
On Wed, 2015-06-10 at 21:27 +0200, Peter Zijlstra wrote:
> On Wed, 2015-06-10 at 14:17 -0500, Scott Wood wrote:
> > On Wed, 2015-06-10 at 13:41 +0200, Peter Zijlstra wrote:
> > > Hi Mike, Ben,
> > >
> > > I just noticed:
> > >
> > > arch/powerpc/Kconfig: select HAVE_PERF_EVENTS_NMI if PPC64
> > >
> > > But can't ppc32 have FSL_EMB perf?
> >
> > Yes, but it doesn't use NMIs. ppc64 has lazy interrupt disabling
> > which functions as a pseudo-NMI.
>
> I know. But you can get the same nesting nonsense as with actual real
> NMIs.
What sort of "nesting nonsense" would we get on ppc32? I wasn't
trying to say that the pseudo-NMIs didn't count -- I was pointing out
that we don't even have that on ppc32.
> And seeing how you select HAVE_PERF_EVENT_NMI for PPC64, I figure you
> ought to select it too for whatever fsl-emb is.
Why?
> # git grep nmi_enter arch/powerpc/
> arch/powerpc/perf/core-book3s.c: nmi_enter();
> arch/powerpc/perf/core-fsl-emb.c: nmi_enter();
nmi_enter() only gets called when perf_intr_is_nmi() returns non-zero,
which only happens on ppc64.
-Scott
next prev parent reply other threads:[~2015-06-10 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 11:41 question on FSL_EMB perf Peter Zijlstra
2015-06-10 19:17 ` Scott Wood
2015-06-10 19:27 ` Peter Zijlstra
2015-06-10 20:13 ` Scott Wood [this message]
2015-06-10 21:14 ` Peter Zijlstra
2015-06-10 21:28 ` Scott Wood
2015-06-11 6:00 ` Michael Ellerman
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=1433967236.2477.146.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=peterz@infradead.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.