From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
qemu-devel@nongnu.org,
Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
Subject: [RFC PATCH 0/4] spapr: clean up nested hv
Date: Wed, 3 May 2023 10:39:50 +1000 [thread overview]
Message-ID: <20230503003954.128188-1-npiggin@gmail.com> (raw)
Something like this is the way I'd been wanting to refactor nested hv.
The state load/store functions and data is (somewhat) abstracted, and
the hcall interface remains in the hcall handlers.
If, hypothetically, you had a new flavour of nested enter hcall that had
some other way of specifying the L2 state to load, then you would
(hopefully) be able to extend and reuse the state struct and load/store
helpers.
Thanks,
Nick
Nicholas Piggin (4):
spapr: H_ENTER_NESTED should restore host XER ca field
spapr: Add a nested state struct
spapr: load and store l2 state with helper functions
spapr: Move spapr nested HV to a new file
hw/ppc/meson.build | 1 +
hw/ppc/spapr_hcall.c | 348 +---------------------
hw/ppc/spapr_nested.c | 496 ++++++++++++++++++++++++++++++++
include/hw/ppc/spapr.h | 61 +---
include/hw/ppc/spapr_cpu_core.h | 5 +-
5 files changed, 502 insertions(+), 409 deletions(-)
create mode 100644 hw/ppc/spapr_nested.c
--
2.40.1
next reply other threads:[~2023-05-03 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 0:39 Nicholas Piggin [this message]
2023-05-03 0:39 ` [RFC PATCH 1/4] spapr: H_ENTER_NESTED should restore host XER ca field Nicholas Piggin
2023-05-05 10:20 ` Harsh Prateek Bora
2023-05-03 0:39 ` [RFC PATCH 2/4] spapr: Add a nested state struct Nicholas Piggin
2023-05-05 10:54 ` Harsh Prateek Bora
2023-05-13 3:27 ` Nicholas Piggin
2023-05-03 0:39 ` [RFC PATCH 3/4] spapr: load and store l2 state with helper functions Nicholas Piggin
2023-05-05 11:03 ` Harsh Prateek Bora
2023-05-13 3:30 ` Nicholas Piggin
2023-05-03 0:39 ` [RFC PATCH 4/4] spapr: Move spapr nested HV to a new file Nicholas Piggin
2023-05-05 11:09 ` Harsh Prateek Bora
2023-05-13 3:32 ` Nicholas Piggin
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=20230503003954.128188-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=harsh@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).