From: Avik Sil <aviksil@linux.vnet.ibm.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: aliguori@us.ibm.com, qemu-ppc@nongnu.org,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/2] Make default boot order machine specific
Date: Wed, 24 Oct 2012 07:27:01 +0530 [thread overview]
Message-ID: <50874AED.7090200@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121023234315.GG13231@truffula.fritz.box>
On 10/24/2012 05:13 AM, David Gibson wrote:
> On Wed, Oct 24, 2012 at 12:47:34AM +0200, Alexander Graf wrote:
>>
>> On 24.10.2012, at 00:43, David Gibson wrote:
>>
>>> 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?
>>
>> I mean that this patch only patches 7 files. Check this out:
>
> Oh, yes, oops. Saw the big pile of hunks changing machines and
> assumed that was all, but in fact half of them were just the PC
> variants.
>
> Avik, this will need to be fixed.
>
Sure, will do. Actually I patched the machines that do care for boot
order like in pc_piix.c and other machines do not care for the order.
But in next series I'll do it for every machine.
Regards,
Avik
next prev parent reply other threads:[~2012-10-24 1:57 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 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-10-23 22:47 ` Alexander Graf
2012-10-23 23:43 ` David Gibson
2012-10-24 1:57 ` Avik Sil [this message]
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=50874AED.7090200@linux.vnet.ibm.com \
--to=aviksil@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=dwg@au1.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).