From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: "Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Fabiano Rosas" <farosas@linux.ibm.com>,
qemu-devel@nongnu.org, "Nicholas Piggin" <npiggin@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>
Subject: [PATCH v2 0/9] ppc: nested KVM HV for spapr virtual hypervisor
Date: Wed, 16 Feb 2022 20:25:36 +1000 [thread overview]
Message-ID: <20220216102545.1808018-1-npiggin@gmail.com> (raw)
This should account for AFAIKS all comments, except maybe some
about naming.
Changes since v1:
- Per-CPU spapr nested state moved to SpaprCpuState from PowerPCCPU.
- address_space_map ops are used, small rearrangement to make any
given access region store-only or load-only.
- Some style, naming, etc cleanups and fixes.
Hopefully I didn't miss anything.
Thanks,
Nick
Nicholas Piggin (9):
target/ppc: raise HV interrupts for partition table entry problems
spapr: prevent hdec timer being set up under virtual hypervisor
ppc: allow the hdecr timer to be created/destroyed
target/ppc: add vhyp addressing mode helper for radix MMU
target/ppc: make vhyp get_pate method take lpid and return success
target/ppc: add helper for books vhyp hypercall handler
target/ppc: Add powerpc_reset_excp_state helper
target/ppc: Introduce a vhyp framework for nested HV support
spapr: implement nested-hv capability for the virtual hypervisor
hw/ppc/pegasos2.c | 6 +
hw/ppc/ppc.c | 23 ++-
hw/ppc/spapr.c | 46 ++++-
hw/ppc/spapr_caps.c | 14 +-
hw/ppc/spapr_cpu_core.c | 6 +-
hw/ppc/spapr_hcall.c | 333 ++++++++++++++++++++++++++++++++
include/hw/ppc/ppc.h | 3 +
include/hw/ppc/spapr.h | 74 ++++++-
include/hw/ppc/spapr_cpu_core.h | 5 +
target/ppc/cpu.h | 10 +-
target/ppc/excp_helper.c | 117 ++++++++---
target/ppc/mmu-radix64.c | 37 +++-
12 files changed, 621 insertions(+), 53 deletions(-)
--
2.23.0
next reply other threads:[~2022-02-16 10:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 10:25 Nicholas Piggin [this message]
2022-02-16 10:25 ` [PATCH v2 1/9] target/ppc: raise HV interrupts for partition table entry problems Nicholas Piggin
2022-02-16 10:25 ` [PATCH v2 2/9] spapr: prevent hdec timer being set up under virtual hypervisor Nicholas Piggin
2022-02-16 10:25 ` [PATCH v2 3/9] ppc: allow the hdecr timer to be created/destroyed Nicholas Piggin
2022-02-16 10:25 ` [PATCH v2 4/9] target/ppc: add vhyp addressing mode helper for radix MMU Nicholas Piggin
2022-02-16 10:25 ` [PATCH v2 5/9] target/ppc: make vhyp get_pate method take lpid and return success Nicholas Piggin
2022-02-16 10:25 ` [PATCH v2 6/9] target/ppc: add helper for books vhyp hypercall handler Nicholas Piggin
2022-02-16 10:25 ` [PATCH v2 7/9] target/ppc: Add powerpc_reset_excp_state helper Nicholas Piggin
2022-02-16 10:25 ` [PATCH v2 8/9] target/ppc: Introduce a vhyp framework for nested HV support Nicholas Piggin
2022-02-16 10:38 ` Cédric Le Goater
2022-02-16 10:25 ` [PATCH v2 9/9] spapr: implement nested-hv capability for the virtual hypervisor Nicholas Piggin
2022-02-16 10:52 ` Cédric Le Goater
2022-02-16 11:38 ` Nicholas Piggin
2022-02-16 12:30 ` Nicholas Piggin
2022-02-17 17:11 ` Cédric Le Goater
2022-02-18 7:45 ` [PATCH v2 0/9] ppc: nested KVM HV for spapr " 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=20220216102545.1808018-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=farosas@linux.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).