qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avik Sil <aviksil@linux.vnet.ibm.com>
To: Chris Wright <chrisw@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>,
	qemu-ppc List <qemu-ppc@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>,
	David Gibson <dwg@au1.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Add nvram to default boot device list
Date: Tue, 16 Oct 2012 17:15:15 +0530	[thread overview]
Message-ID: <507D48CB.5070506@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121012030249.GW27180@x200.localdomain>

On 10/12/2012 08:32 AM, Chris Wright wrote:
> * Alexander Graf (agraf@suse.de) wrote:
>> On 12.10.2012, at 02:28, David Gibson wrote:
>>> On Fri, Oct 12, 2012 at 02:03:00AM +0200, 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?
>>>
>>> Uh, is this a call I know about?
>>
>> I would hope so. Chris / Juan, who is in charge of the phone numbers these days?
> 
> Added David to the invite which contains the call details (very
> unfriendly time for .au I'm afraid, 14:00 UTC).
> 
Is it OK if I proxy David as it's unfriendly time for him? Also can this
topic be included in today's call?

Regards,
Avik

  reply	other threads:[~2012-10-16 11:45 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 [this message]
2012-10-16  3:44     ` Avik Sil
2012-10-16  8:04       ` Alexander Graf
2012-10-16  8:37         ` Andreas Färber
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=507D48CB.5070506@linux.vnet.ibm.com \
    --to=aviksil@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=chrisw@redhat.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 \
    --cc=quintela@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).