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
Subject: Re: [PATCH] docs: Update POWER9 XIVE support for nested guests
Date: Wed, 5 Aug 2020 11:51:22 +1000 [thread overview]
Message-ID: <20200805015122.GB2178@yekko.fritz.box> (raw)
In-Reply-To: <20200804131639.407049-1-clg@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On Tue, Aug 04, 2020 at 03:16:39PM +0200, Cédric Le Goater wrote:
> It is not yet supported.
>
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Applied to ppc-for-5.2.
> ---
> docs/specs/ppc-spapr-xive.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/docs/specs/ppc-spapr-xive.rst b/docs/specs/ppc-spapr-xive.rst
> index 6159bc6eed62..7199db730b82 100644
> --- a/docs/specs/ppc-spapr-xive.rst
> +++ b/docs/specs/ppc-spapr-xive.rst
> @@ -61,6 +61,11 @@ depend on the XIVE KVM capability of the host. On older kernels
> without XIVE KVM support, QEMU will use the emulated XIVE device as a
> fallback and on newer kernels (>=5.2), the KVM XIVE device.
>
> +XIVE native exploitation mode is not supported for KVM nested guests,
> +VMs running under a L1 hypervisor (KVM on pSeries). In that case, the
> +hypervisor will not advertise the KVM capability and QEMU will use the
> +emulated XIVE device, same as for older versions of KVM.
> +
> As a final refinement, the user can also switch the use of the KVM
> device with the machine option ``kernel_irqchip``.
>
--
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 --]
prev parent reply other threads:[~2020-08-05 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 13:16 [PATCH] docs: Update POWER9 XIVE support for nested guests Cédric Le Goater
2020-08-05 1:51 ` David Gibson [this message]
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=20200805015122.GB2178@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@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).