[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: |
Sat, 7 Sep 2013 10:19:52 +0100 |
On 7 September 2013 10:13, Laurent Vivier <address@hidden> wrote:
> Le 07/09/2013 10:43, Peter Maydell a écrit :
> In fact, I don't understand why a given CPU id has been chosen to be the
> default value. I think there is a default value not because this is the
> best/most used value but because we need a default.
The default for ARM is "any", which is specifically for linux-user
and means "enable all possible user-visible instruction set options".
That means it should be able to run any guest binary OK.
Some other target CPU types do this, but not all; I think that
ideally we should convert them to do similarly.
I agree that the cases where we've picked some specific CPU
to be the linux-user default are a bit dubious.
-- 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