From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC PATCH 3/3] spapr: generate a CAS reset for the XIVE exploitation mode
Date: Sun, 10 Sep 2017 13:19:42 +1000 [thread overview]
Message-ID: <20170910031942.GZ2735@umbus.fritz.box> (raw)
In-Reply-To: <20170908143344.12960-4-clg@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 2517 bytes --]
On Fri, Sep 08, 2017 at 04:33:44PM +0200, Cédric Le Goater wrote:
> When the platform and the guest agree on using the XIVE exploitation
> mode for interrupts, the "interrupt-controller" node needs to reflect
> the change and the device tree needs an update.
>
> Reseting the guest after the CAS negotiation makes this change
> possible, as the device tree is built at reset time. We use the
> 'ov5_cas' field to check which interrupt model was negotiated before
> reset and populate the tree accordingly.
>
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Looks reasonable, though I'm not going to apply it until we actually
have something to go..
> ---
> hw/ppc/spapr.c | 6 +++++-
> hw/ppc/spapr_hcall.c | 6 ++++++
> 2 files changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index 3e3ff1fbc988..be467ab61ad0 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -1073,7 +1073,11 @@ static void *spapr_build_fdt(sPAPRMachineState *spapr,
> _FDT(fdt_setprop_cell(fdt, 0, "#size-cells", 2));
>
> /* /interrupt controller */
> - spapr_dt_xics(xics_max_server_number(), fdt, PHANDLE_XICP);
> + if (!spapr_ovec_test(spapr->ov5_cas, OV5_XIVE_EXPLOIT)) {
> + spapr_dt_xics(xics_max_server_number(), fdt, PHANDLE_XICP);
> + } else {
> + /* populate device tree for XIVE */ ;
.. here.
> + }
>
> ret = spapr_populate_memory(spapr, fdt);
> if (ret < 0) {
> diff --git a/hw/ppc/spapr_hcall.c b/hw/ppc/spapr_hcall.c
> index 92f1e21358b8..ba00b8d3fdd6 100644
> --- a/hw/ppc/spapr_hcall.c
> +++ b/hw/ppc/spapr_hcall.c
> @@ -1613,6 +1613,12 @@ static target_ulong h_client_architecture_support(PowerPCCPU *cpu,
> (spapr_h_cas_compose_response(spapr, args[1], args[2],
> ov5_updates) != 0);
> }
> +
> + /* We need to rebuild the device tree for XIVE, generate a reset */
> + if (!spapr->cas_reboot) {
> + spapr->cas_reboot = spapr_ovec_test(ov5_updates, OV5_XIVE_EXPLOIT);
> + }
At some point we may well want to make XIVE exploitation the default
for POWER9 guests, but that's a detail easily adjusted later.
> spapr_ovec_cleanup(ov5_updates);
>
> if (spapr->cas_reboot) {
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-10 3:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 14:33 [Qemu-devel] [PATCH 0/3] spapr: XIVE and CAS fixes Cédric Le Goater
2017-09-08 14:33 ` [Qemu-devel] [PATCH 1/3] ppc/xive: fix OV5_XIVE_EXPLOIT bits Cédric Le Goater
2017-09-08 16:24 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2017-09-10 3:16 ` [Qemu-devel] " David Gibson
2017-09-08 14:33 ` [Qemu-devel] [PATCH 2/3] spapr: fix CAS-generated reset Cédric Le Goater
2017-09-10 3:17 ` David Gibson
2017-09-10 19:23 ` Cédric Le Goater
2017-09-08 14:33 ` [Qemu-devel] [RFC PATCH 3/3] spapr: generate a CAS reset for the XIVE exploitation mode Cédric Le Goater
2017-09-10 3:19 ` David Gibson [this message]
2017-09-10 19:30 ` Cédric Le Goater
2017-09-11 3:54 ` David Gibson
2017-09-09 5:57 ` [Qemu-devel] [Qemu-ppc] [PATCH 0/3] spapr: XIVE and CAS fixes 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=20170910031942.GZ2735@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=mdroth@linux.vnet.ibm.com \
--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).