[Top][All Lists]

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

Re: [Qemu-devel] [PATCH] linux-user: Support explicit targets for PowerP

From: Aaron Sierra
Subject: Re: [Qemu-devel] [PATCH] linux-user: Support explicit targets for PowerPC
Date: Tue, 7 Nov 2017 09:25:16 -0600 (CST)

----- Original Message -----
> From: "Peter Maydell" <address@hidden>
> Sent: Tuesday, November 7, 2017 3:29:21 AM

> On 7 November 2017 at 06:57, Laurent Vivier <address@hidden> wrote:
>> Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
>>> Enable building PowerPC targets supporting a specific CPU, without
>>> having to set QEMU_CPU via the environment. For example these build
>>> targets (and many more) become available:
>>>     qemu-ppc.e500mc
>>>     qemu-ppc.e500v2
>>>     qemu-ppc.e5500
>>>     qemu-ppc.e600
>>>     qemu-ppc.e6500
>>> These (statically compiled) binaries have proven useful for emulating
>>> PowerPC CPUs within Docker containers, where it's hard to reliably
>>> define environment variables that are available for every process.
>> I agree with you.
>> I have patches to do that for years, perhaps we can merge our both
>> solutions to have something working:
>> linux-user: define default cpu model in configure instead of
>> linux-user/main.c
>> https://github.com/vivier/qemu-m68k/commit/1488df8c9fa3a5b099bbc4f41c077a6c69305cc2
>> linux-user: specify the cpu model during configure
>> https://github.com/vivier/qemu-m68k/commit/496f804fd97d5f0ef26da1090e1d95ad15bcc50e
>> The part missing in my series is to rename the qemu binaries with the
>> suffix of the default CPU.
> I don't really like this -- it means we'll end up with a huge
> extra range of executables, and every time a new CPU type is
> added a new binary has to be plumbed in to our own 'make
> install' machinery and into every distro's packaging.


Yes, there is a huge new range of binaries (there's actually no practical
upper bound), but I don't really anticipate this feature being used en masse
by distributions. I do see it as a very useful tool for developers to be
able to leverage when the situation arises.

-Aaron S.

> The 'look at argv[0]' approach is perhaps a bit more
> palatable. Or you could just write and use wrapper
> scripts.
> I take it there's no good "-cpu any" option for PPC that
> would run all these binaries?
> thanks
> -- PMM

reply via email to

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