From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: patches@linaro.org
Subject: Re: [Qemu-devel] [maybe-for-2.0 0/2] hw/arm: Don't specify any default board
Date: Wed, 26 Mar 2014 10:53:35 +0100 [thread overview]
Message-ID: <5332A39F.6010609@redhat.com> (raw)
In-Reply-To: <1395775613-30984-1-git-send-email-peter.maydell@linaro.org>
Il 25/03/2014 20:26, Peter Maydell ha scritto:
> Currently for both qemu-system-arm and qemu-system-aarch64
> the default board model if the user doesn't specify one
> is the 'integratorcp'. This is a totally arbitrary historical
> accident since it was the first board to be modelled.
> That board is now just one target among many for us, and
> is a very poor choice of default:
> * it's an ancient board that is now only found in the
> junkpiles of longtime ARM/Linux hackers, if at all
> * it's an ARMv5 CPU, when most distros are now assuming ARMv7
> * it's pretty much unmaintained in QEMU
> * it doesn't even have versatilepb's advantage of supporting PCI
>
> Making it or any other board the default serves only to confuse
> people new to ARM who expect something more like the x86 monoculture,
> and try to run a Linux kernel built for some random devboard on
> QEMU's integratorcp model by mistake
>
> This series removes the is_default marker from integratorcp,
> to give users a nudge that they need to think about which board
> they want a QEMU model of.
>
> Since it's now more likely that users will hit it, patch 2
> improves the slightly cryptic error "No machine found." to
> align with the rather more helpful text produced if you ask
> -M no-such-machine.
>
> This is a little late in the 2.0 cycle, but on the other hand
> the patches themselves are trivially simple, and the only
> question really is if we want to do this. It does break
> backwards compatibility of command lines with anybody who
> is still really running integratorcp kernels and not bothering
> to specify "-M integratorcp". But 2.0 is a nice round number
> to do that, and I think we improve usability for people who
> don't realise that the default is wrong for 99%+ of users.
>
> Peter Maydell (2):
> hw/arm: Stop specifying integratorcp as the default board
> vl.c: Improve message when no default machine is found
>
> hw/arm/integratorcp.c | 1 -
> vl.c | 3 ++-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
series
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2014-03-26 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 19:26 [Qemu-devel] [maybe-for-2.0 0/2] hw/arm: Don't specify any default board Peter Maydell
2014-03-25 19:26 ` [Qemu-devel] [maybe-for-2.0 1/2] hw/arm: Stop specifying integratorcp as the " Peter Maydell
2014-03-28 11:17 ` [Qemu-devel] [maybe-for-2.0 1/2] hw/arm: Stop specifyingintegratorcp as the default boardd Alex Bennée
2014-03-28 11:35 ` Peter Maydell
2014-03-25 19:26 ` [Qemu-devel] [maybe-for-2.0 2/2] vl.c: Improve message when no default machine is found Peter Maydell
2014-03-26 19:22 ` Marcel Apfelbaum
2014-03-28 11:16 ` [Qemu-devel] [maybe-for-2.0 2/2] vl.c: Improve message when nodefault machine is foundd Alex Bennée
2014-03-26 9:53 ` Paolo Bonzini [this message]
2014-03-26 15:16 ` [Qemu-devel] [maybe-for-2.0 0/2] hw/arm: Don't specify any default board 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=5332A39F.6010609@redhat.com \
--to=pbonzini@redhat.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).