From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: kvm-ppc@vger.kernel.org, "Nicholas Piggin" <npiggin@gmail.com>,
"Paul Mackerras" <paulus@samba.org>,
"Cédric Le Goater" <clg@kaod.org>,
"Anton Blanchard" <anton@linux.ibm.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PATCH v2 0/3] powerpc/pseries: IPI doorbell improvements
Date: Tue, 30 Jun 2020 21:50:30 +1000 [thread overview]
Message-ID: <20200630115034.137050-1-npiggin@gmail.com> (raw)
Since v1:
- Fixed SMP compile error.
- Fixed EPAPR / KVM_GUEST breakage.
- Expanded patch 3 changelog a bit.
Thanks,
Nick
Nicholas Piggin (3):
powerpc: inline doorbell sending functions
powerpc/pseries: Use doorbells even if XIVE is available
powerpc/pseries: Add KVM guest doorbell restrictions
arch/powerpc/include/asm/dbell.h | 63 ++++++++++++++++++++++++++--
arch/powerpc/include/asm/firmware.h | 6 +++
arch/powerpc/include/asm/kvm_para.h | 26 ++----------
arch/powerpc/kernel/Makefile | 5 +--
arch/powerpc/kernel/dbell.c | 55 ------------------------
arch/powerpc/kernel/firmware.c | 19 +++++++++
arch/powerpc/platforms/pseries/smp.c | 62 +++++++++++++++++++--------
7 files changed, 134 insertions(+), 102 deletions(-)
--
2.23.0
next reply other threads:[~2020-06-30 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 11:50 Nicholas Piggin [this message]
2020-06-30 11:50 ` [PATCH v2 1/3] powerpc: inline doorbell sending functions Nicholas Piggin
2020-07-22 0:52 ` Michael Ellerman
2020-06-30 11:50 ` [PATCH v2 2/3] powerpc/pseries: Use doorbells even if XIVE is available Nicholas Piggin
2020-06-30 11:50 ` [PATCH v2 3/3] powerpc/pseries: Add KVM guest doorbell restrictions Nicholas Piggin
2020-07-23 17:18 ` [PATCH v2 0/3] powerpc/pseries: IPI doorbell improvements Cédric Le Goater
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=20200630115034.137050-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=anton@linux.ibm.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).