From: "Cédric Le Goater" <clg@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
qemu-ppc@nongnu.org, "Greg Kurz" <groug@kaod.org>,
"Gustavo Romero" <gromero@linux.ibm.com>
Subject: [PATCH 0/8] spapr/xive: Activate StoreEOI in P10 compat guests
Date: Wed, 19 Aug 2020 15:08:35 +0200 [thread overview]
Message-ID: <20200819130843.2230799-1-clg@kaod.org> (raw)
Hello,
The first patch is a little improvement on how we deal with priorities
reserved by the hypervisor. The rest is about activating StoreEOI safely
on a host supporting it, P10 hosts are the target but experimental
P9 firmwares activate also StoreEOI.
The patchset adds a new KVM device command KVM_DEV_XIVE_GRP_SOURCE_INFO
(yet to be sent but nothing really complex) which lets QEMU query the
XIVE characteristics of the underlying HW interrupts. It also enforces
StoreEOI on P10 compat guests only to make sure that P9 compat guests
can not be migrated to a P9 host with StoreEOI activated. Nevertheless,
as this is useful, a new Spapr IRQ backend 'xive-storeeoi' allows the
user run a P9 compat guest with StoreEOI enabled.
Please comment because there might be a better alternative to address
these needs.
Thanks,
C.
Cédric Le Goater (8):
spapr/xive: Add a 'hv-prio' property to represent the KVM escalation
priority
linux-headers: Update for KVM_DEV_XIVE_GRP_SOURCE_INFO
spapr/xive: Query the characteristics of a source in KVM
spapr/xive: Activate StoreEOI for POWER10 only
spapr/xive: Enforce the load-after-store ordering
spapr/xive: Activate StoreEOI by default
spapr/xive: Use the xics flag to check for XIVE-only IRQ backends
spapr/xive: Introduce a XIVE StoreEOI IRQ backend
include/hw/ppc/spapr_irq.h | 1 +
include/hw/ppc/spapr_xive.h | 5 +++
include/hw/ppc/xive.h | 8 +++++
linux-headers/asm-powerpc/kvm.h | 8 +++++
hw/intc/spapr_xive.c | 56 ++++++++++++++++++++++-----------
hw/intc/spapr_xive_kvm.c | 38 ++++++++++++++++++++++
hw/intc/xive.c | 6 ++++
hw/ppc/spapr.c | 6 +++-
hw/ppc/spapr_irq.c | 36 ++++++++++++++++++++-
9 files changed, 143 insertions(+), 21 deletions(-)
--
2.25.4
next reply other threads:[~2020-08-19 13:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 13:08 Cédric Le Goater [this message]
2020-08-19 13:08 ` [PATCH 1/8] spapr/xive: Add a 'hv-prio' property to represent the KVM escalation priority Cédric Le Goater
2020-08-20 0:58 ` David Gibson
2020-08-19 13:08 ` [PATCH 2/8] linux-headers: Update for KVM_DEV_XIVE_GRP_SOURCE_INFO Cédric Le Goater
2020-08-20 0:58 ` David Gibson
2020-08-20 6:49 ` Cédric Le Goater
2020-08-19 13:08 ` [PATCH 3/8] spapr/xive: Query the characteristics of a source in KVM Cédric Le Goater
2020-08-20 1:33 ` David Gibson
2020-08-20 6:58 ` Cédric Le Goater
2020-08-19 13:08 ` [PATCH 4/8] spapr/xive: Activate StoreEOI for POWER10 only Cédric Le Goater
2020-08-19 13:08 ` [PATCH 5/8] spapr/xive: Enforce the load-after-store ordering Cédric Le Goater
2020-08-19 13:08 ` [PATCH 6/8] spapr/xive: Activate StoreEOI by default Cédric Le Goater
2020-08-19 13:08 ` [PATCH 7/8] spapr/xive: Use the xics flag to check for XIVE-only IRQ backends Cédric Le Goater
2020-08-20 1:36 ` David Gibson
2020-08-20 6:59 ` Cédric Le Goater
2020-08-19 13:08 ` [PATCH 8/8] spapr/xive: Introduce a XIVE StoreEOI IRQ backend 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=20200819130843.2230799-1-clg@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=gromero@linux.ibm.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).