From: Nicholas Piggin <npiggin@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc/64s: Use relon prolog for EXC_VIRT_OOL_MASKABLE_HV handlers
Date: Sat, 15 Apr 2017 20:31:57 +1000 [thread overview]
Message-ID: <20170415203157.779872d1@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <877f2o8mdw.fsf@concordia.ellerman.id.au>
On Thu, 13 Apr 2017 23:31:23 +1000
Michael Ellerman <mpe@ellerman.id.au> wrote:
> Nicholas Piggin <npiggin@gmail.com> writes:
>
> > Hypervisor Virtualization and Directed Hypervisor Doorbell interrupt
> > handlers use the macro EXC_VIRT_OOL_MASKABLE_HV for their relocation-on
> > handlers, which calls MASKABLE_RELON_EXCEPTION_HV_OOL, which uses the
> > real mode interrupt prolog.
> >
> > Use the RELON variant instead to reduce overhead.
> >
> > Fixes: 1707dd1613 ("powerpc: Save CFAR before branching in interrupt entry paths")
> > Cc: Paul Mackerras <paulus@samba.org>
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> >
> > I was hesitant about using the Fixes: tag on this one because it's not
> > a correctness bug as far as I can see.
>
> Fixes can just mean "if you have this other commit you'll most likely
> want this one too".
>
> You can clarify the degree of Fixness in the change log, which then
> allows a backporter to decide if they want it or not.
>
> In this case I think it's entirely right, this is a fairly unfortunate
> bug from a performance point of view if I'm reading it right.
Okay, makes sense. For POWER8 it only affects doorbell IPIs. Context switch
microbenchmark between threads with snooze disabled (which causes IPI) gets
about 3% faster, about 370 cycles. Should be more important on POWER9 with
global doorbells and HVI for host interrupts.
Thanks,
Nick
next prev parent reply other threads:[~2017-04-15 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 9:45 [PATCH] powerpc/64s: Use relon prolog for EXC_VIRT_OOL_MASKABLE_HV handlers Nicholas Piggin
2017-04-13 13:31 ` Michael Ellerman
2017-04-15 10:31 ` Nicholas Piggin [this message]
2017-04-21 4:09 ` 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=20170415203157.779872d1@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.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).