qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, paulus@ozlabs.org
Subject: Re: [Qemu-devel] [QEMU-PPC] [PATCH V3 0/3] ppc/spapr: Add support for nested kvm-hv
Date: Wed, 7 Nov 2018 15:48:59 +1100	[thread overview]
Message-ID: <20181107044859.GF5575@umbus.fritz.box> (raw)
In-Reply-To: <20181011061609.11423-1-sjitindarsingh@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

On Thu, Oct 11, 2018 at 05:16:06PM +1100, Suraj Jitindar Singh wrote:
> This patch series adds the qemu support for running nested kvm-hv on a
> POWER9 platform with appropriate hypervisor support and migration of
> these guests.
> That is, the ability to run kvm-hv guests as guests of an operating system
> which is itself a kvm-hv guest.
> 
> The host (L0 hypervisor) and level 1 guest (L1 guest hypervisor) require
> the following patch series:
> KVM: PPC: Book3S HV: Nested HV virtualization
> 
> And this patch series in the qemu instance running on the L0 hypervisor.
> 
> Patch series based on: ppc-for-3.1
> 
> The cap number is now in Paolo's tree so hopefully we can rely on it not
> changing.

Now that the kernel changes are in upstream master, can you resend a
final version of this?

> 
> V2 -> V3:
> - The enable cap ioctl no longer takes an enable field to indicate
>   disable/enable, but just enables the cap. So update to match this
>   kernel change. (The cap starts out disable by default)
> 
> Suraj Jitindar Singh (3):
>   target/ppc: Update linux-headers for v4.19-rc7
>   target/ppc: Add one reg id for ptcr
>   ppc/spapr_caps: Add SPAPR_CAP_NESTED_KVM_HV
> 
>  hw/ppc/spapr.c                  |  2 ++
>  hw/ppc/spapr_caps.c             | 32 ++++++++++++++++++++++++++++++++
>  include/hw/ppc/spapr.h          |  5 ++++-
>  linux-headers/asm-powerpc/kvm.h |  1 +
>  linux-headers/linux/kvm.h       |  1 +
>  target/ppc/kvm.c                | 12 ++++++++++++
>  target/ppc/kvm_ppc.h            | 12 ++++++++++++
>  target/ppc/translate_init.inc.c | 10 +++++-----
>  8 files changed, 69 insertions(+), 6 deletions(-)
> 

-- 
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 --]

      parent reply	other threads:[~2018-11-07  4:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11  6:16 [Qemu-devel] [QEMU-PPC] [PATCH V3 0/3] ppc/spapr: Add support for nested kvm-hv Suraj Jitindar Singh
2018-10-11  6:16 ` [Qemu-devel] [QEMU-PPC] [PATCH V3 1/3] target/ppc: Update linux-headers for v4.19-rc7 Suraj Jitindar Singh
2018-10-11  6:16 ` [Qemu-devel] [QEMU-PPC] [PATCH V3 2/3] target/ppc: Add one reg id for ptcr Suraj Jitindar Singh
2018-10-11  6:16 ` [Qemu-devel] [QEMU-PPC] [PATCH V3 3/3] ppc/spapr_caps: Add SPAPR_CAP_NESTED_KVM_HV Suraj Jitindar Singh
2018-11-07  4:48 ` 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=20181107044859.GF5575@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=paulus@ozlabs.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=sjitindarsingh@gmail.com \
    /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).