From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48153) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TK3xl-00023Q-26 for qemu-devel@nongnu.org; Fri, 05 Oct 2012 05:12:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TK3xe-0002HC-Ve for qemu-devel@nongnu.org; Fri, 05 Oct 2012 05:12:52 -0400 Received: from e23smtp04.au.ibm.com ([202.81.31.146]:56143) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TK3xe-0002GT-Dz for qemu-devel@nongnu.org; Fri, 05 Oct 2012 05:12:46 -0400 Received: from /spool/local by e23smtp04.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 5 Oct 2012 19:09:18 +1000 Message-ID: <1349428350.4260.67.camel@pasglop> From: Benjamin Herrenschmidt Date: Fri, 05 Oct 2012 19:12:30 +1000 In-Reply-To: References: <50641A82.4030708@linux.vnet.ibm.com> <1348738150.24701.21.camel@pasglop> <20120927095136.GI23096@redhat.com> <506D6B20.7020508@linux.vnet.ibm.com> <20121005003416.GS29302@truffula.fritz.box> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel qemu-devel , "qemu-ppc@nongnu.org List" , Avik Sil , Gleb Natapov , David Gibson 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.