qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	"Richard W.M. Jones" <rjones@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option
Date: Mon, 25 Jul 2011 14:18:00 +0200	[thread overview]
Message-ID: <4E2D5EF8.5000507@siemens.com> (raw)
In-Reply-To: <CAFEAcA81om5n0hH2o8z5WEO9QBDGn3QYgntrXhzrHpAfHe9Z7w@mail.gmail.com>

On 2011-07-25 14:05, Peter Maydell wrote:
> On 25 July 2011 12:48, Peter Maydell <peter.maydell@linaro.org> wrote:
>> For ARM you absolutely should not be relying on the default
>> machine type (not least because it's an incredibly ancient
>> dev board which nobody uses any more). An ARM kernel is
>> generally fairly specific to the hardware platform being
>> emulated, so you should know which machine you're intending
>> to run on and specify it explicitly.
> 
> In fact having thought about it a bit I'm going to go further
> and say that the whole idea of a "default machine" is a rather
> x86-centric idea -- most architectures don't really have a
> single machine type that's used by just about everybody,
> always has been, and isn't likely to become obsolete in the
> future. So if we're reworking the command line API to
> supersede "-M" then we shouldn't have a default at all.

Then you may want to drop is_default = 1 from integratorcp and prepare
the main loop to face a NULL machine.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-07-25 12:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 10:38 [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Jan Kiszka
2011-07-23 10:39 ` [Qemu-devel] [RESEND][PATCH 2/2] Deprecate -M command line options Jan Kiszka
2011-07-23 15:43 ` [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Anthony Liguori
2011-07-25  9:41 ` Richard W.M. Jones
2011-07-25 10:33   ` Jan Kiszka
2011-07-25 10:45     ` Richard W.M. Jones
2011-07-25 10:59       ` Jan Kiszka
2011-07-25 11:39         ` Markus Armbruster
2011-07-25 11:48           ` Jan Kiszka
2011-07-25 16:11             ` [Qemu-devel] [PATCH] Allow to leave type on default in -machine Jan Kiszka
2011-07-25 16:21               ` Richard W.M. Jones
2011-07-25 16:33                 ` Alexander Graf
2011-07-29 14:37               ` Anthony Liguori
2011-07-25 12:23         ` [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Anthony Liguori
2011-07-25 11:48       ` Peter Maydell
2011-07-25 12:05         ` Peter Maydell
2011-07-25 12:18           ` Jan Kiszka [this message]
2011-07-25 12:22             ` Peter Maydell
2011-07-25 12:27               ` Jan Kiszka
2011-07-25 12:44           ` Alexander Graf
2011-07-25 12:47             ` Anthony Liguori
2011-07-25 12:49               ` Richard W.M. Jones
2011-07-25 12:53                 ` Alexander Graf

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=4E2D5EF8.5000507@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=aliguori@us.ibm.com \
    --cc=anthony.perard@citrix.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    /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).