From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Paul Mackerras <paulus@ozlabs.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [PATCH 0/5] doorbell patches for POWER9
Date: Fri, 7 Apr 2017 22:55:05 +1000 [thread overview]
Message-ID: <20170407125510.30991-1-npiggin@gmail.com> (raw)
This is what I'd like to do for POWER9 doorbells, which reworks
the existing code a bit. I guess it won't work on DD1 with OPAL
until darn is fixed (only tested on POWER9 using mambo).
Nicholas Piggin (5):
powerpc/pseries: do not use msgsndp doorbells on POWER9 guests
powerpc: change the doorbell IPI calling convention
powerpc: Introduce msgsnd/doorbell barrier primitives
powerpc/64s: avoid branch for ppc_msgsnd
powerpc/powernv: POWER9 support for msgsnd/doorbell IPI
arch/powerpc/include/asm/dbell.h | 45 ++++++++++++++++++------
arch/powerpc/include/asm/feature-fixups.h | 20 +++++++++++
arch/powerpc/include/asm/ppc-opcode.h | 6 ++++
arch/powerpc/include/asm/ppc_asm.h | 15 ++++++++
arch/powerpc/include/asm/smp.h | 4 +--
arch/powerpc/include/asm/xics.h | 2 +-
arch/powerpc/kernel/dbell.c | 58 +++++++++++++++++++++++++++----
arch/powerpc/kernel/smp.c | 27 +++++++-------
arch/powerpc/platforms/85xx/smp.c | 11 ++----
arch/powerpc/platforms/powermac/smp.c | 2 +-
arch/powerpc/platforms/powernv/smp.c | 33 +++++++++++++-----
arch/powerpc/platforms/pseries/smp.c | 33 ++++++++----------
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 --
16 files changed, 189 insertions(+), 86 deletions(-)
--
2.11.0
next reply other threads:[~2017-04-07 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 12:55 Nicholas Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-07 12:55 [PATCH 0/5] doorbell patches for POWER9 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=20170407125510.30991-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@ozlabs.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).