qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs


From: Greg Kurz
Subject: Re: [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs
Date: Mon, 15 Jan 2018 12:05:43 +0100

On Mon, 15 Jan 2018 10:30:53 +0100
Thomas Huth <address@hidden> wrote:

> ppc64-softmmu is a superset of ppc-softmmu which in turn is a superset

Hi Thomas,

Per curiosity. I understand that a 64-bit ppc CPU is expected to support
32-bit ppc code, but does QEMU really need to emulate setups that likely
never existed in real life (like a PowerMac G5 or a pSeries with an
internal floppy disk controller for example) ?

I ask because Murilo and I had a chat about removing CONFIG_FDC from
default-configs/ppc64-softmmu.mak the other day :)

Cheers,

--
Greg

> of ppcemb-softmmu. But since the config files are currently independent
> from each other, we missed to define some CONFIG switches in the super-
> sets: CONFIG_SUNGEM is missing from the ppc64-softmmu config, and the
> CONFIG_IDE_SII3112 switch is only defined in ppcemb-softmmu.
> 
> Let's fix this by including the subsets instead of duplicating all the
> switches all over the place.
> 
> (off-topic question: Do we still need a separate ppcemb-softmmu nowadays?
> It seemed to be useful 10 years ago when everybody was doing KVM on
> embedded PPC, but these days seem to be pretty much over now, so IMHO
> just using ppc-softmmu for embedded should be enough nowadays? We could
> save quite some compilation- and "make check"-time if we could finally get
> rid of ppcemb-softmmu again...)
> 
> Thomas Huth (2):
>   default-configs/ppc64-softmmu: Include 32-bit configs instead of
>     copying them
>   default-configs/ppc-softmmu: Restructure the switches according to the
>     machines
> 
>  default-configs/ppc-softmmu.mak   | 59 +++++++++++++++----------------------
>  default-configs/ppc64-softmmu.mak | 61 
> +++++----------------------------------
>  2 files changed, 32 insertions(+), 88 deletions(-)
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]