From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCHv4 15/15] Pass boot device list to firmware. Date: Tue, 16 Nov 2010 21:02:46 +0200 Message-ID: <20101116190246.GA27851@redhat.com> References: <1289749181-12070-1-git-send-email-gleb@redhat.com> <1289749181-12070-16-git-send-email-gleb@redhat.com> <20101115084242.GG7948@redhat.com> <20101116141112.GS7948@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, armbru@redhat.com, alex.williamson@redhat.com, mst@redhat.com, kevin@koconnor.net To: Blue Swirl Return-path: Received: from mx1.redhat.com ([209.132.183.28]:38860 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755076Ab0KPTCv convert rfc822-to-8bit (ORCPT ); Tue, 16 Nov 2010 14:02:51 -0500 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Nov 16, 2010 at 06:30:19PM +0000, Blue Swirl wrote: > >> Perhaps the FW path should use device class names if no name is sp= ecified. > > What do you mean by "device class name". We can do something like t= his: > > if (dev->child_bus.lh_first) > > =9A =9A =9A =9Areturn dev->child_bus.lh_first->info->name; > > > > i.e if there is child bus use its bus name as fw name. This will ma= ke > > all pci devices to have "pci" as fw name automatically. The problem= is > > that theoretically same device can provide different buses. >=20 > I meant PCI class name, like "display" for display controllers, > "network" for NICs etc. >=20 That is what my pci bus related patch is doing already. > >> I'll try Sparc32 to see how this fits there. >=20 > Except bootindex is not implemented for SCSI. Will look into adding it. -- Gleb.