From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
qemu-ppc@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Cédric Le Goater" <clg@kaod.org>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH 0/4] hw/ppc/spapr: Rename SoftMMU -> TCG
Date: Mon, 2 Oct 2023 16:38:50 +0200 [thread overview]
Message-ID: <20231002143855.50978-1-philmd@linaro.org> (raw)
We want to clarify when code depends on a software
MMU, or when it depends on TCG system emulation.
This series renames the 'softmmu' mentions in PPC.
Philippe Mathieu-Daudé (4):
hw/ppc/spapr: Add missing license
hw/ppc/spapr_hcall: Allow elision of softmmu_resize_hpt_prepare/commit
hw/ppc/spapr_hcall: Rename {softmmu ->
tcgppc}_resize_hpt_prepare/commit
hw/ppc/spapr: Rename 'softmmu' -> 'tcg'
include/hw/ppc/spapr.h | 8 ++++----
hw/ppc/spapr_hcall.c | 12 ++++++++----
hw/ppc/{spapr_softmmu.c => spapr_tcg.c} | 9 +++++++++
target/ppc/tcg-stub.c | 15 ---------------
hw/ppc/meson.build | 2 +-
5 files changed, 22 insertions(+), 24 deletions(-)
rename hw/ppc/{spapr_softmmu.c => spapr_tcg.c} (98%)
--
2.41.0
next reply other threads:[~2023-10-02 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:38 Philippe Mathieu-Daudé [this message]
2023-10-02 14:38 ` [PATCH 1/4] hw/ppc/spapr: Add missing license Philippe Mathieu-Daudé
2023-10-02 14:38 ` [PATCH 2/4] hw/ppc/spapr_hcall: Allow elision of softmmu_resize_hpt_prepare/commit Philippe Mathieu-Daudé
2023-10-02 14:38 ` [PATCH 3/4] hw/ppc/spapr_hcall: Rename {softmmu -> tcgppc}_resize_hpt_prepare/commit Philippe Mathieu-Daudé
2023-10-03 2:03 ` David Gibson
2023-10-02 14:38 ` [PATCH 4/4] hw/ppc/spapr: Rename 'softmmu' -> 'tcg' Philippe Mathieu-Daudé
2023-10-03 2:07 ` David Gibson
2023-10-18 12:58 ` 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=20231002143855.50978-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.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).