linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: <ananth@in.ibm.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: Tue, 1 Sep 2015 19:03:12 -0500	[thread overview]
Message-ID: <1441152192.4966.103.camel@freescale.com> (raw)
In-Reply-To: <20150901064113.GA1196@in.ibm.com>

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:
> > > Add user return notifier support for powerpc. Similar to x86, this 
> > > feature
> > > keys off of the KVM Kconfig.
> > 
> > Please flesh this out.
> > 
> > What is it, why do we want it, why is your implementation correct.
> 
> The only current in-kernel user of the infrastructure is KVM on x86. It
> is useful for optimizations when MSR values can continue to be used
> between the host and guest. Commit log for 18863bdd60f8 upstream has a
> more complete explanation.
>
> I do not know the inner details of the KVM implementation on Power,
> perhaps Paul/Gautham can comment on if a similar optimization will
> benefit Power systems too?

"MSR" is x86-specific terminology and is pretty vague.  What specifically is 
the functionality being optimized, in terms of things that actually exist on 
PPC?

In any case, that commit log doesn't explain what user-return-notifier is or 
how it works, just that it's being used.

> 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?

-Scott

  reply	other threads:[~2015-09-02  1:37 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 [this message]
2015-09-02  2:37       ` Ananth N Mavinakayanahalli
2015-09-02  3:29         ` Scott Wood
2015-09-02  5:09           ` Ananth N Mavinakayanahalli
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=1441152192.4966.103.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=ananth@in.ibm.com \
    --cc=ego@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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 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).