[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 0/4] Define default CPU at configure time
From: |
Peter Maydell |
Subject: |
Re: [Qemu-devel] [PATCH 0/4] Define default CPU at configure time |
Date: |
Tue, 10 Sep 2013 09:40:04 +0100 |
On 10 September 2013 08:13, Laurent Vivier <address@hidden> wrote:
>> Le 9 septembre 2013 à 21:23, Richard Henderson <address@hidden> a écrit :
>> For mips this is impossible. There are multiple isa extensions that are
>> mutually exclusive. But for everyone else that ought to work.
>
> It doesn't work for m68k, too. It's why I need to define the default I want
> to use...
Where the instruction set options conflict I really
don't think we should have a default selectable at
configure time. Having different people with different
qemu-m68k or qemu-mips being able to run or not run
different programs sounds very confusing. At least if
there's a command line option or a wrapper to set
environment then it's reasonably clear that the
config is different. Also if these different
variants are properly represented by different ELF
information you can then register several different
wrappers to handle different flavours of m68k
or mips binary correctly.
-- PMM
- [Qemu-devel] [PATCH 0/4] Define default CPU at configure time, Laurent Vivier, 2013/09/06
- [Qemu-devel] [PATCH 1/4] linux-user: define default cpu model in configure instead of linux-user/main.c, Laurent Vivier, 2013/09/06
- [Qemu-devel] [PATCH 2/4] linux-user: specify the cpu model during configure, Laurent Vivier, 2013/09/06
- [Qemu-devel] [PATCH 4/4] linux-user,arm: display default cpu, Laurent Vivier, 2013/09/06
- [Qemu-devel] [PATCH 3/4] linux-user,m68k: display default cpu, Laurent Vivier, 2013/09/06
- Re: [Qemu-devel] [PATCH 0/4] Define default CPU at configure time, Peter Maydell, 2013/09/07