qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	Benjamin Herrenschmidt <benh@au1.ibm.com>,
	"qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>,
	Alexander Graf <agraf@suse.de>,
	Avik Sil <aviksil@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting
Date: Thu, 27 Sep 2012 12:38:31 +0200	[thread overview]
Message-ID: <20120927103831.GN23096@redhat.com> (raw)
In-Reply-To: <87a9wbhhyp.fsf@linux.vnet.ibm.com>

On Thu, Sep 27, 2012 at 04:04:54PM +0530, Nikunj A Dadhania wrote:
> On Thu, 27 Sep 2012 12:13:05 +0200, Gleb Natapov <gleb@redhat.com> wrote:
> > On Thu, Sep 27, 2012 at 03:35:53PM +0530, Nikunj A Dadhania wrote:
> > > 
> > > If the user does not set bootindex, qemu would decide the bootindex?  
> > > 
> > No. Firmware decides. QEMU just tells to firmware that it does not have
> > bootindex.
> 
> Ok. That should work in that case, we need to make sure that bootindex
> is being send via device-tree. I do not see such code in place
> currently.
> 
It is sent to firmware via PV fw_cfg interface in "bootorder" file.

> > 
> > > If it does, there will be a default bootindex. Then the problem still
> > > remains, qemu decided the boot-order, in which case we would want to
> > > pick the nvram based setting. This is again difficult to distinguish.
> > > 
> > > > There is nothing "blurry" about OF device
> > > > path. The problem is that it works reasonably well with legacy BIOS
> > > > since it is enough to specify device to boot from, but with EFI (OF is
> > > > the same I guess) it is not enough to point to a device to boot from,
> > > > but you also need to specify a file you want to boot and this is where
> > > > bootindex approach fails.
> > > 
> > > By file I suppose you mean OF device-path. 
> > > 
> > No. By file I mean a file on dedicated EFI FAT partition that EFI loads
> > during boot.  I do not know if OF has something similar.
> > 
> No, it just needs the device-path. Rest it figures out.
> 
> Regards
> Nikunj

--
			Gleb.

  reply	other threads:[~2012-09-27 10:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50641A82.4030708@linux.vnet.ibm.com>
     [not found] ` <1348738150.24701.21.camel@pasglop>
2012-09-27  9:33   ` [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting Alexander Graf
2012-09-27  9:35     ` Benjamin Herrenschmidt
2012-09-27  9:39       ` Alexander Graf
2012-09-27  9:51     ` Gleb Natapov
2012-09-27 10:05       ` Nikunj A Dadhania
2012-09-27 10:13         ` Gleb Natapov
2012-09-27 10:34           ` Nikunj A Dadhania
2012-09-27 10:38             ` Gleb Natapov [this message]
2012-09-27 10:21       ` Benjamin Herrenschmidt
2012-09-27 10:35         ` Gleb Natapov
2012-09-28  6:12       ` Jordan Justen
2012-10-04 10:55       ` Avik Sil
2012-10-04 11:22         ` Gleb Natapov
2012-10-04 11:29           ` Avik Sil
2012-10-04 11:30             ` Alexander Graf
2012-10-04 12:18               ` Avik Sil
2012-10-04 12:21                 ` Alexander Graf
2012-10-04 12:35                   ` Avik Sil
2012-10-04 12:37                     ` Alexander Graf
2012-10-04 12:38                       ` Gleb Natapov
2012-10-05  4:45                       ` Nikunj A Dadhania
2012-10-04 11:32             ` Gleb Natapov
2012-10-04 11:59               ` Avik Sil
2012-10-05  0:34         ` David Gibson
2012-10-05  0:43           ` Alexander Graf
2012-10-05  0:48             ` David Gibson
2012-10-05  9:12             ` Benjamin Herrenschmidt
2012-10-05 10:32               ` Alexander Graf
2012-10-05  5:30           ` Nikunj A Dadhania
2012-10-05  5:44             ` 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=20120927103831.GN23096@redhat.com \
    --to=gleb@redhat.com \
    --cc=agraf@suse.de \
    --cc=aviksil@linux.vnet.ibm.com \
    --cc=benh@au1.ibm.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).