From: Laurent Vivier <Laurent@Vivier.EU>
To: Peter Maydell <peter.maydell@linaro.org>
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, 07 Sep 2013 11:13:17 +0200 [thread overview]
Message-ID: <522AEE2D.1090408@Vivier.EU> (raw)
In-Reply-To: <CAFEAcA_0adu3fQA1kxZkWHpSMgfcQAOyoQ2dN14XS9DwoxANFg@mail.gmail.com>
Le 07/09/2013 10:43, Peter Maydell a écrit :
> On 6 September 2013 21:47, Laurent Vivier <laurent@vivier.eu> wrote:
>> This series of patch allows to set the default CPU used by linux-user qemu.
>>
>> When qemu is used in a container as a binfmt interpreter we can't use the
>> environment variable QEMU_CPU to set the CPU id.
> I definitely don't like this. We shouldn't be hardcoding this at
> configure time. There doesn't seem to be any particular reason
> why QEMU_CPU is the only option you might want to set for
> your binfmt-interpreter either.
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. It's hardcoded at
development time. So I think this is better to be able to choose this
default value without editing any file. A configuration option is the
best solution for me. Moreover, this doesn't change the default behavior.
> Is there a reason why using a wrapper script which sets
> options to the real qemu binary won't work?
Personal reason : I don't like wrapper. Kernel must load two
executables, wrapper must analyze environment, auxv, parameters and pass
what it needs to pass.
But I don't want to push these patches at any reason : I just want to share.
Thank you for your comments.
Regards,
Laurent
next prev parent reply other threads:[~2013-09-07 9:13 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 [this message]
2013-09-07 9:19 ` Peter Maydell
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=522AEE2D.1090408@Vivier.EU \
--to=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--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).