From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC][PATCH 0/2] reworking cause_ipi and adding global doorbell support
Date: Tue, 14 Mar 2017 10:31:08 +1100 [thread overview]
Message-ID: <1489447868.2174.16.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170312171327.21088-1-npiggin@gmail.com>
On Mon, 2017-03-13 at 03:13 +1000, Nicholas Piggin wrote:
> Hi,
>
> Just after the previous two fixes, I would like to propose changing
> the way we do doorbell vs interrupt controller IPIs, and add support
> for global doorbells supported by POWER9 in HV mode.
>
> After this, the platform code knows about doorbells and interrupt
> controller IPIs, rather than they know about each other.
A few things come to mind:
- We don't want to use doorbells under KVM. They are going to turn
into traps and be emulated, slower than using H_IPI, at least on P9.
Even for core only doorbells. I'm not sure how to convey that to the
guest.
- On PP9 DD1 we need a CI load instead of msgsync (a DARN instruction
would do too if it works)
- Can we get rid of the atomic ops for manipulating the IPI mux ? What
about a cache line per message and just set/clear ? If we clear in the
doorbell handler before we call the respective targets, we shouldn't
"lose" messages no ? As long as the actual handlers "loop" as necessary
of course.
Cheers,
Ben.
> Thanks,
> Nick
>
> Nicholas Piggin (2):
> powerpc/64s: change the doorbell IPI calling convention
> powerpc/64s: use global doorbell on POWER9 in HV mode
>
> arch/powerpc/include/asm/dbell.h | 38 ++++++++++++++++++++++
> -----
> arch/powerpc/include/asm/smp.h | 4 +--
> arch/powerpc/include/asm/xics.h | 2 +-
> arch/powerpc/kernel/dbell.c | 47 ++++++++++++++++++++++
> ------------
> arch/powerpc/kernel/smp.c | 27 ++++++++++---------
> arch/powerpc/platforms/85xx/smp.c | 9 +------
> arch/powerpc/platforms/powermac/smp.c | 2 +-
> arch/powerpc/platforms/powernv/smp.c | 32 +++++++++++++++++------
> arch/powerpc/platforms/pseries/smp.c | 28 ++++++++------------
> arch/powerpc/sysdev/xics/icp-hv.c | 2 +-
> arch/powerpc/sysdev/xics/icp-native.c | 12 +--------
> arch/powerpc/sysdev/xics/icp-opal.c | 2 +-
> arch/powerpc/sysdev/xics/xics-common.c | 3 ---
> 13 files changed, 118 insertions(+), 90 deletions(-)
>
next prev parent reply other threads:[~2017-03-14 0:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 17:13 [RFC][PATCH 0/2] reworking cause_ipi and adding global doorbell support Nicholas Piggin
2017-03-12 17:13 ` [PATCH 1/2] powerpc/64s: change the doorbell IPI calling convention Nicholas Piggin
2017-03-12 17:13 ` [PATCH 2/2] powerpc/64s: use global doorbell on POWER9 in HV mode Nicholas Piggin
2017-03-13 23:31 ` Benjamin Herrenschmidt [this message]
2017-03-14 1:49 ` [RFC][PATCH 0/2] reworking cause_ipi and adding global doorbell support Nicholas Piggin
2017-03-14 2:34 ` Benjamin Herrenschmidt
2017-03-14 2:53 ` Nicholas Piggin
2017-03-14 3:57 ` Benjamin Herrenschmidt
2017-03-14 4:35 ` Nicholas Piggin
2017-03-14 4:50 ` Benjamin Herrenschmidt
2017-03-14 6:22 ` Nicholas Piggin
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=1489447868.2174.16.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).