From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Richard Henderson <rth@twiddle.net>, Jia Liu <proljc@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name
Date: Mon, 22 Jul 2013 12:34:56 +0100 [thread overview]
Message-ID: <CAFEAcA9U0jEumpyEzuUXc9Ce4+NAhGD7zmi-713wx0RMCOcL2Q@mail.gmail.com> (raw)
In-Reply-To: <51ED14BD.8050406@suse.de>
On 22 July 2013 12:17, Andreas Färber <afaerber@suse.de> wrote:
> Am 22.07.2013 12:40, schrieb Peter Maydell:
>> Yep; my view is that the acceptance of the -or32-cpu varieties
>> was a bug which we have now fixed. In any case we should be
>> consistent across target architectures about what we allow.
>> I'm happy with the approach Jia has taken of just dropping
>> this patch in v4 of this series.
>
> alpha allows both, but -cpu ? just gave me a segfault. :/
Odd; that works for me:
cam-vm-266:precise:qemu$ ./build/x86-all/alpha-softmmu/qemu-system-alpha -cpu ?
Available CPUs:
ev4-alpha-cpu
ev5-alpha-cpu
ev56-alpha-cpu
ev6-alpha-cpu
ev67-alpha-cpu
ev68-alpha-cpu
pca56-alpha-cpu
> It didn't have -cpu ? before QOM, so we decided to print the type names
> there.
Looking at all of the '-cpu help' output, alpha seems to be
the odd one out here: none of the others list valid CPUs
with "-$arch-cpu" suffixes.
> Stripping -alpha-cpu off typenames would surely be possible.
I think that that would be better in the name of consistency.
Also regarding consistency, not all targets react very well
to being asked for a nonexistent cpu via "-cpu xyzzy":
alpha and s390x just plough on without an error
lm32 and unicore32 segfault
(some of this may be default board model bugs rather than
target-* bugs).
-- PMM
next prev parent reply other threads:[~2013-07-22 11:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 8:56 [Qemu-devel] [PATCH v3 0/4] target-openrisc hw/openrisc: Some OpenRISC fix Jia Liu
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 1/4] hw/openrisc: Indent typo Jia Liu
2013-07-22 9:21 ` Peter Maydell
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 2/4] hw/openrisc: Use stderr output instead of qemu_log Jia Liu
2013-07-22 9:21 ` Peter Maydell
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 3/4] target-openrisc: Free typename Jia Liu
2013-07-22 9:37 ` Jia Liu
2013-07-22 9:41 ` Peter Maydell
2013-07-22 9:43 ` Jia Liu
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Jia Liu
2013-07-22 9:29 ` Peter Maydell
2013-07-22 9:42 ` Jia Liu
2013-07-22 9:43 ` Peter Maydell
2013-07-22 9:54 ` Jia Liu
2013-07-22 10:12 ` Jia Liu
2013-07-22 10:37 ` Andreas Färber
2013-07-22 10:40 ` Peter Maydell
2013-07-22 11:17 ` Andreas Färber
2013-07-22 11:34 ` Peter Maydell [this message]
2013-07-22 12:26 ` [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Andreas Färber
2013-07-22 12:33 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Andreas Färber
2013-07-22 15:25 ` Anthony Liguori
2013-07-22 15:38 ` Peter Maydell
2013-07-22 16:29 ` [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Andreas Färber
2013-07-22 17:39 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Anthony Liguori
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=CAFEAcA9U0jEumpyEzuUXc9Ce4+NAhGD7zmi-713wx0RMCOcL2Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).