From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>, <linuxppc-dev@ozlabs.org>,
"Paul Mackerras" <paulus@samba.org>, <ego@linux.vnet.ibm.com>
Subject: Re: powerpc: Add user-return-notifier support
Date: Wed, 2 Sep 2015 10:39:58 +0530 [thread overview]
Message-ID: <20150902050958.GC1196@in.ibm.com> (raw)
In-Reply-To: <1441164552.4966.153.camel@freescale.com>
On Tue, Sep 01, 2015 at 10:29:12PM -0500, Scott Wood wrote:
> On Wed, 2015-09-02 at 08:07 +0530, Ananth N Mavinakayanahalli wrote:
> > On Tue, Sep 01, 2015 at 07:03:12PM -0500, Scott Wood wrote:
> > > On Tue, 2015-09-01 at 12:11 +0530, Ananth N Mavinakayanahalli wrote:
> > > > On Mon, Aug 31, 2015 at 08:35:17PM +1000, Michael Ellerman wrote:
> > > > > On Tue, 2015-25-08 at 05:41:10 UTC, Ananth N Mavinakayanahalli wrote:
...
> > > > We could certainly make this a generic config option.. but I am yet to
> > > > see a real usecase outside of the KVM thingy. We do use TIF_UPROBE for
> > > > something very similar, though that needs to fire much before the
> > > > outstanding signals get handled. The user-return notifier is the last
> > > > thing executed before return to userspace -- the two cannot be merged.
> > > >
> > > > Ananth
> > > >
> > > > PS: I am not sure having an 'ok' against the Documentation/features/ for
> > > > powerpc is a valid enough argument for this :-)
> > >
> > > So how did you test this? What platforms did you test it on? What
> > > hardware
> > > support does it need?
> >
> > Simple kernel module below... Its fairly evident from the patch that the
> > feature is a software only construct and no specific hardware support is
> > needed.
>
> It's evident now that I'm aware of what the purpose is... It wasn't 100%
>
> clear before, at least from a quick glance, given that the explanation was
>
> "look at this hardware-specific KVM patch", whether there was an assumption
> of something else going on -- and even things that are implemented in
> software often work differently on book3s versus book3e, ppc32 versus ppc64,
> etc.
I meant the infrastructure is agnostic of the underlying Power platform.
Sorry if I wasn't clear.
> Why is this selected by KVM on PPC if KVM on PPC doesn't use it? What is the
> user you're trying to enable?
I copied Paul and Gautham to get their thoughts on whether it is
something they could use on Power. At this time, apart from enabling the
feature, I do not have a specific usecase for it. We can park this patch
pending a real user on powerpc.
> Where is the "profiler" that Documentation/features/debug/user-ret-
> profiler/arch-support.txt hints at?
I guess profiler is a misnomer. Not sure why it was named that and not a
notifier.
Ananth
next prev parent reply other threads:[~2015-09-02 5:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 5:41 [PATCH] powerpc: Add user-return-notifier support Ananth N Mavinakayanahalli
2015-08-31 10:35 ` Michael Ellerman
2015-09-01 6:41 ` Ananth N Mavinakayanahalli
2015-09-02 0:03 ` Scott Wood
2015-09-02 2:37 ` Ananth N Mavinakayanahalli
2015-09-02 3:29 ` Scott Wood
2015-09-02 5:09 ` Ananth N Mavinakayanahalli [this message]
2015-09-08 9:24 ` Michael Ellerman
2015-09-08 10:51 ` Ananth N Mavinakayanahalli
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=20150902050958.GC1196@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).