From: David Gibson <dwg@au1.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: aliguori@us.ibm.com, qemu-ppc@nongnu.org,
Avik Sil <aviksil@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/2] Make default boot order machine specific
Date: Wed, 24 Oct 2012 09:43:51 +1100 [thread overview]
Message-ID: <20121023224351.GE13231@truffula.fritz.box> (raw)
In-Reply-To: <1A23CBFB-5BF8-45A3-A7FB-9E00E6D18AA1@suse.de>
On Tue, Oct 23, 2012 at 12:20:08PM +0200, Alexander Graf wrote:
>
> On 23.10.2012, at 12:09, Avik Sil wrote:
>
> > This patch makes default boot order machine specific instead of
> > set globally. The default boot order can be set per machine in
> > QEMUMachine default_machine_opts, or by the command line using
> > -machine <machine_name>,boot=<boot_devices>, or by standard -boot
> > option. This allows a machine to receive a NULL boot order when
> > -boot isn't used and take an appropriate action accordingly. This
> > helps machine boots from the devices as set in guest's non-volatile
> > memory location in case no boot order is provided by the user.
> >
> > Signed-off-by: Avik Sil <aviksil@linux.vnet.ibm.com>
> > ---
> > hw/nseries.c | 2 ++
> > hw/pc_piix.c | 13 ++++++++++++-
> > hw/ppc_newworld.c | 1 +
> > hw/ppc_oldworld.c | 1 +
> > hw/ppc_prep.c | 1 +
> > hw/sun4m.c | 10 ++++++++++
> > hw/sun4u.c | 3 +++
>
> That feels like too much magic for my taste. Can't we have some
> default macro (or even the explicit "cad" thing) that we push to
> _every_ machine description out there? The next patch to implement
> boot= for pseries would then remove this default value for the
> pseries machine.
I'm not 100% clear on what you mean here. Do you just mean:
#define DEFAULT_BOOT_ORDER "boot=cad"
and then we use
.default_machine_opts = DEFAULT_BOOT_ORDER,
or something else?
> The way the patch works right now, the "make machine specific" patch
> indirectly also changes the behavior for a bunch of machines.
A bunch? I thought the only machine whose behaviour changed was
pseries. I agree that moving the behaviour change into a separate
patch would be a better idea, but if there are machines other than
pseries with changed behaviour by this patch, then that's a plain old
bug, rather than a mere question of patch elegance.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-10-23 22:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 10:09 [Qemu-devel] [PATCH 0/2] Qemu boot order patch series Avik Sil
2012-10-23 10:09 ` [Qemu-devel] [PATCH 1/2] Make default boot order machine specific Avik Sil
2012-10-23 10:20 ` Alexander Graf
2012-10-23 13:24 ` Anthony Liguori
2012-10-23 13:28 ` Alexander Graf
2012-10-23 22:43 ` David Gibson [this message]
2012-10-23 22:47 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2012-10-23 23:43 ` David Gibson
2012-10-24 1:57 ` Avik Sil
2012-10-23 10:09 ` [Qemu-devel] [PATCH 2/2] pseries: set boot-device property only if boot order specified Avik Sil
2012-10-23 22:45 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-10-24 2:01 ` Avik Sil
2012-10-24 3:54 ` David Gibson
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=20121023224351.GE13231@truffula.fritz.box \
--to=dwg@au1.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=aviksil@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).