From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>,
Avik Sil <aviksil@linux.vnet.ibm.com>,
Gleb Natapov <gleb@redhat.com>, David Gibson <dwg@au1.ibm.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting
Date: Fri, 05 Oct 2012 19:12:30 +1000 [thread overview]
Message-ID: <1349428350.4260.67.camel@pasglop> (raw)
In-Reply-To: <EC718CF7-AD5E-41FD-820B-5A568735F058@suse.de>
On Fri, 2012-10-05 at 02:43 +0200, Alexander Graf wrote:
> > We should also be able to get the raw bootindex values for a qdev,
> > yes? I was thinking we could instead copy those values into the
> > device tree when we populate it. The trouble is that we don't
> > actually generate (in qemu) nodes for individual disks under a
> vscsi,
> > or for individual PCI devices under the host bridge (that's done by
> > SLOF). Still thinking...
>
> Well. You can track it down to the device level and you know the drive
> index. Maybe you could be clever if you had a device property that
> contains the drive index and boot index to it?
You can but it's hard... eventually we'll do it but it will take some
time. In the meantime, a patch allowing us know whether -boot was
specified at all or not would be handy to make things work as expected
in the most common cases.
Avik & Nikunj are going to send one if not already...
Cheers,
Ben.
next prev parent reply other threads:[~2012-10-05 9:12 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
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 [this message]
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=1349428350.4260.67.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=agraf@suse.de \
--cc=aviksil@linux.vnet.ibm.com \
--cc=dwg@au1.ibm.com \
--cc=gleb@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.