From: Peter Maydell <peter.maydell@linaro.org>
To: Laurent Vivier <Laurent@vivier.eu>
Cc: Riku Voipio <riku.voipio@iki.fi>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/4] Define default CPU at configure time
Date: Sat, 7 Sep 2013 10:19:52 +0100 [thread overview]
Message-ID: <CAFEAcA9zQLUJzCfQSJMvoeia4=2S2J2wGadnq4spVponeZE18A@mail.gmail.com> (raw)
In-Reply-To: <522AEE2D.1090408@Vivier.EU>
On 7 September 2013 10:13, Laurent Vivier <Laurent@vivier.eu> 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
next prev parent reply other threads:[~2013-09-07 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 20:47 [Qemu-devel] [PATCH 0/4] Define default CPU at configure time Laurent Vivier
2013-09-06 20:47 ` [Qemu-devel] [PATCH 1/4] linux-user: define default cpu model in configure instead of linux-user/main.c Laurent Vivier
2013-09-06 20:47 ` [Qemu-devel] [PATCH 2/4] linux-user: specify the cpu model during configure Laurent Vivier
2013-09-06 20:47 ` [Qemu-devel] [PATCH 3/4] linux-user,m68k: display default cpu Laurent Vivier
2013-09-06 20:47 ` [Qemu-devel] [PATCH 4/4] linux-user,arm: " Laurent Vivier
2013-09-07 8:43 ` [Qemu-devel] [PATCH 0/4] Define default CPU at configure time Peter Maydell
2013-09-07 9:13 ` Laurent Vivier
2013-09-07 9:19 ` Peter Maydell [this message]
2013-09-09 19:23 ` Richard Henderson
2013-09-10 7:13 ` Laurent Vivier
2013-09-10 8:40 ` Peter Maydell
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='CAFEAcA9zQLUJzCfQSJMvoeia4=2S2J2wGadnq4spVponeZE18A@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=Laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).