From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Gleb Natapov <gleb@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
David Gibson <dwg@au1.ibm.com>,
qemu-ppc List <qemu-ppc@nongnu.org>,
Avik Sil <aviksil@linux.vnet.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] Add nvram to default boot device list
Date: Tue, 16 Oct 2012 10:37:40 +0200 [thread overview]
Message-ID: <507D1CD4.7070504@suse.de> (raw)
In-Reply-To: <80A8CD3C-C79E-45F8-8861-EEB37272D2B1@suse.de>
Am 16.10.2012 10:04, schrieb Alexander Graf:
>
>
> On 16.10.2012, at 05:44, Avik Sil <aviksil@linux.vnet.ibm.com> wrote:
>
>> On 10/12/2012 05:33 AM, Alexander Graf wrote:
>>>
>>> On 12.10.2012, at 00:59, David Gibson wrote:
>>>
>>>> On Thu, Oct 11, 2012 at 07:34:42AM +0530, Avik Sil wrote:
>>>>> This patch adds nvram specified boot device into qemu default
>>>>> boot_devices list. This helps firmware to boot from nvram specified
>>>>> boot device if no -boot option is specified.
>>>>
>>>> I really don't think this is a good idea, it extends an already
>>>> deprecated mechanism in a fuzzy way and requires careful checking to
>>>> see if it could break anything. On all platforms the boot sequence
>>>> should be:
>>>> if bootindex is specified:
>>>> boot according to bootindex
>>>> else if -boot is specified:
>>>> boot according to -boot sequence
>>>> else:
>>>> use platform firmware default sequence
>>>>
>>>> The last will of course vary by platform, and could depend on platform
>>>> details like the contents of NVRAM. Your original idea of making it
>>>> clear to the guest when -boot has been specified (as opposed to when
>>>> it contains its default value) was the right one, and this "x" in
>>>> -boot is going the wrong direction.
>>>
>>> Given that this is a fundamental direction for a bunch of machines, how about we talk about it on the weekly QEMU call?
>>>
>> Was there any discussion on this in the last QEMU call?
>
> The call is today :)
...and the topic is not officially on the agenda yet. :)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-10-16 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 2:04 [Qemu-devel] [PATCH] Add nvram to default boot device list Avik Sil
2012-10-11 12:48 ` Alexander Graf
2012-10-11 22:59 ` David Gibson
2012-10-12 0:03 ` Alexander Graf
2012-10-12 0:28 ` David Gibson
2012-10-12 0:29 ` Alexander Graf
2012-10-12 3:02 ` Chris Wright
2012-10-16 11:45 ` Avik Sil
2012-10-16 3:44 ` Avik Sil
2012-10-16 8:04 ` Alexander Graf
2012-10-16 8:37 ` Andreas Färber [this message]
2012-10-12 7:12 ` Avik Sil
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=507D1CD4.7070504@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=aviksil@linux.vnet.ibm.com \
--cc=dwg@au1.ibm.com \
--cc=gleb@redhat.com \
--cc=nikunj@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).