From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
qemu-devel@nongnu.org, Harsh Prateek Bora <harshpb@linux.ibm.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>
Subject: [PATCH v2 0/4] ppc/spapr: Nested HV fix and tidying
Date: Tue, 20 Jun 2023 20:57:33 +1000 [thread overview]
Message-ID: <20230620105737.160451-1-npiggin@gmail.com> (raw)
To prepare for some later changes to nested-HV I would like to get
these cleanups done and move nested to its own file. This is
rebased and patch 4 has some nested function definitions and
structs in spapr_nested.h that Harsh suggested.
Thanks,
Nick
Nicholas Piggin (4):
ppc/spapr: H_ENTER_NESTED should restore host XER ca field
ppc/spapr: Add a nested state struct
ppc/spapr: load and store l2 state with helper functions
ppc/spapr: Move spapr nested HV to a new file
hw/ppc/meson.build | 1 +
hw/ppc/spapr.c | 1 +
hw/ppc/spapr_hcall.c | 335 +--------------------------
hw/ppc/spapr_nested.c | 395 ++++++++++++++++++++++++++++++++
include/hw/ppc/spapr.h | 62 -----
include/hw/ppc/spapr_cpu_core.h | 5 +-
include/hw/ppc/spapr_nested.h | 102 +++++++++
7 files changed, 504 insertions(+), 397 deletions(-)
create mode 100644 hw/ppc/spapr_nested.c
create mode 100644 include/hw/ppc/spapr_nested.h
--
2.40.1
next reply other threads:[~2023-06-20 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:57 Nicholas Piggin [this message]
2023-06-20 10:57 ` [PATCH v2 1/4] ppc/spapr: H_ENTER_NESTED should restore host XER ca field Nicholas Piggin
2023-06-20 10:57 ` [PATCH v2 2/4] ppc/spapr: Add a nested state struct Nicholas Piggin
2023-06-20 10:57 ` [PATCH v2 3/4] ppc/spapr: load and store l2 state with helper functions Nicholas Piggin
2023-06-20 10:57 ` [PATCH v2 4/4] ppc/spapr: Move spapr nested HV to a new file Nicholas Piggin
2023-06-21 6:45 ` Harsh Prateek Bora
2023-06-23 9:30 ` [PATCH v2 0/4] ppc/spapr: Nested HV fix and tidying 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=20230620105737.160451-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=danielhb413@gmail.com \
--cc=harshpb@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).