From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Cc: mikey@neuling.org, vaibhav@linux.ibm.com, jniethe5@gmail.com,
sbhat@linux.ibm.com, kconsul@linux.vnet.ibm.com,
dbarboza@ventanamicro.com, npiggin@gmail.com
Subject: [PATCH 00/15] Nested PAPR API (KVM on PowerVM)
Date: Tue, 18 Jul 2023 14:52:06 +0530 [thread overview]
Message-ID: <20230718092221.1053686-1-harshpb@linux.ibm.com> (raw)
There is an existing Nested-HV API to enable nested guests on powernv
machines. However, that is not supported on pseries/PowerVM LPARs.
This patch series implements required hcall interfaces to enable nested
guests with KVM on PowerVM.
Unlike Nested-HV, with this API, entire L2 state is retained by L0
during guest entry/exit and uses pre-defined Guest State Buffer (GSB)
format to communicate guest state between L1 and L2 via L0.
L0 here refers to the phyp/PowerVM, or launching a Qemu TCG L0 with the
newly introduced option cap-nested-papr=true (refer patch 5/15).
L1 refers to the LPAR host on PowerVM or Linux booted on Qemu TCG with
above mentioned option cap-nested-papr=true.
L2 refers to nested guest running on top of L1 using KVM.
No SW changes needed for Qemu running in L1 Linux as well as L2 Kernel.
There is a Linux Kernel side patch series to enable support for Nested
PAPR in L1 and same can be found at below url:
Linux Kernel RFC PATCH v2:
- https://lore.kernel.org/linuxppc-dev/20230605064848.12319-1-jpn@linux.vnet.ibm.com/
For more details, documentation can be referred in either of patch series.
There are scripts available to assist in setting up an environment for
testing nested guests at https://github.com/mikey/kvm-powervm-test
Thanks to Michael Neuling, Shivaprasad Bhat, Kautuk Consul, Vaibhav Jain
and Jordan Niethe.
Harsh Prateek Bora (15):
ppc: spapr: Introduce Nested PAPR API related macros
ppc: spapr: Add new/extend structs to support Nested PAPR API
ppc: spapr: Use SpaprMachineStateNested's ptcr instead of nested_ptcr
ppc: spapr: Start using nested.api for nested kvm-hv api
ppc: spapr: Introduce cap-nested-papr for nested PAPR API
ppc: spapr: Implement nested PAPR hcall - H_GUEST_GET_CAPABILITIES
ppc: spapr: Implement nested PAPR hcall - H_GUEST_SET_CAPABILITIES
ppc: spapr: Implement nested PAPR hcall - H_GUEST_CREATE
ppc: spapr: Implement nested PAPR hcall - H_GUEST_CREATE_VCPU
ppc: spapr: Initialize the GSB Elements lookup table.
ppc: spapr: Implement nested PAPR hcall - H_GUEST_[GET|SET]_STATE
ppc: spapr: Use correct source for parttbl info for nested PAPR API.
ppc: spapr: Implement nested PAPR hcall - H_GUEST_RUN_VCPU
ppc: spapr: Implement nested PAPR hcall - H_GUEST_DELETE
ppc: spapr: Document Nested PAPR API
docs/devel/nested-papr.txt | 500 ++++++++++
hw/ppc/spapr.c | 28 +-
hw/ppc/spapr_caps.c | 50 +
hw/ppc/spapr_hcall.c | 1 +
hw/ppc/spapr_nested.c | 1504 +++++++++++++++++++++++++++++--
include/hw/ppc/ppc.h | 2 +
include/hw/ppc/spapr.h | 35 +-
include/hw/ppc/spapr_cpu_core.h | 7 +-
include/hw/ppc/spapr_nested.h | 378 ++++++++
target/ppc/cpu.h | 2 +
10 files changed, 2433 insertions(+), 74 deletions(-)
create mode 100644 docs/devel/nested-papr.txt
--
2.39.3
next reply other threads:[~2023-07-18 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 9:22 Harsh Prateek Bora [this message]
2023-07-18 9:22 ` [PATCH 01/15] ppc: spapr: Introduce Nested PAPR API related macros Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 02/15] ppc: spapr: Add new/extend structs to support Nested PAPR API Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 03/15] ppc: spapr: Use SpaprMachineStateNested's ptcr instead of nested_ptcr Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 04/15] ppc: spapr: Start using nested.api for nested kvm-hv api Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 05/15] ppc: spapr: Introduce cap-nested-papr for nested PAPR API Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 06/15] ppc: spapr: Implement nested PAPR hcall - H_GUEST_GET_CAPABILITIES Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 07/15] ppc: spapr: Implement nested PAPR hcall - H_GUEST_SET_CAPABILITIES Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 08/15] ppc: spapr: Implement nested PAPR hcall - H_GUEST_CREATE Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 09/15] ppc: spapr: Implement nested PAPR hcall - H_GUEST_CREATE_VCPU Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 10/15] ppc: spapr: Initialize the GSB Elements lookup table Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 11/15] ppc: spapr: Implement nested PAPR hcall - H_GUEST_[GET|SET]_STATE Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 12/15] ppc: spapr: Use correct source for parttbl info for nested PAPR API Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 13/15] ppc: spapr: Implement nested PAPR hcall - H_GUEST_RUN_VCPU Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 14/15] ppc: spapr: Implement nested PAPR hcall - H_GUEST_DELETE Harsh Prateek Bora
2023-07-18 9:22 ` [PATCH 15/15] ppc: spapr: Document Nested PAPR API Harsh Prateek Bora
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 4:33 [PATCH 00/15] Nested PAPR API (KVM on PowerVM) Harsh Prateek Bora
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=20230718092221.1053686-1-harshpb@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=dbarboza@ventanamicro.com \
--cc=jniethe5@gmail.com \
--cc=kconsul@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sbhat@linux.ibm.com \
--cc=vaibhav@linux.ibm.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).