From: "Nicholas Piggin" <npiggin@gmail.com>
To: "David Gibson" <david@gibson.dropbear.id.au>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>
Subject: Re: [PATCH 4/4] hw/ppc/spapr: Rename 'softmmu' -> 'tcg'
Date: Wed, 18 Oct 2023 22:58:16 +1000 [thread overview]
Message-ID: <CWBKZPU8DSYO.GHTQKPP8DSQ2@wheely> (raw)
In-Reply-To: <ZRt3cnl0fH0sBupE@zatzit>
On Tue Oct 3, 2023 at 12:07 PM AEST, David Gibson wrote:
> On Mon, Oct 02, 2023 at 04:38:54PM +0200, Philippe Mathieu-Daudé wrote:
> > spapr_softmmu.c isn't related to having a soft MMU, but having
> > the TCG accelerator. Rename it using the 'tcg' suffix.
>
> That's not really accurate. The functions in there absolutely are
> about the emulated MMU. They're not needed for KVM, because KVM has
> its own MMU emulation, but they're not strictly speaking related to TCG.
Not sure what to do with these.
The spapr facilities names AFAIK don't really differentiate between
when they are supplied for KVM vs TCG, so we could use spapr_mmu.c
or spapr_hpt.c. Or leave as softmmu? Anyone have preferences? I like
hpt.
softmmu_resize_hpt_* could go to spapr_resize_hpt_*
Thanks,
Nick
>
> >
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> > ---
> > hw/ppc/{spapr_softmmu.c => spapr_tcg.c} | 0
> > hw/ppc/meson.build | 2 +-
> > 2 files changed, 1 insertion(+), 1 deletion(-)
> > rename hw/ppc/{spapr_softmmu.c => spapr_tcg.c} (100%)
> >
> > diff --git a/hw/ppc/spapr_softmmu.c b/hw/ppc/spapr_tcg.c
> > similarity index 100%
> > rename from hw/ppc/spapr_softmmu.c
> > rename to hw/ppc/spapr_tcg.c
> > diff --git a/hw/ppc/meson.build b/hw/ppc/meson.build
> > index 7c2c52434a..281100a58d 100644
> > --- a/hw/ppc/meson.build
> > +++ b/hw/ppc/meson.build
> > @@ -31,7 +31,7 @@ ppc_ss.add(when: 'CONFIG_PSERIES', if_true: files(
> > 'pef.c',
> > ))
> > ppc_ss.add(when: ['CONFIG_PSERIES', 'CONFIG_TCG'], if_true: files(
> > - 'spapr_softmmu.c',
> > + 'spapr_tcg.c',
> > ))
> > ppc_ss.add(when: 'CONFIG_SPAPR_RNG', if_true: files('spapr_rng.c'))
> > ppc_ss.add(when: ['CONFIG_PSERIES', 'CONFIG_LINUX'], if_true: files(
prev parent reply other threads:[~2023-10-18 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:38 [PATCH 0/4] hw/ppc/spapr: Rename SoftMMU -> TCG Philippe Mathieu-Daudé
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 [this message]
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=CWBKZPU8DSYO.GHTQKPP8DSQ2@wheely \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=harshpb@linux.ibm.com \
--cc=philmd@linaro.org \
--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).