From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [SeaBIOS] [PATCHv6 00/16] boot order specification Date: Sun, 28 Nov 2010 21:52:13 +0200 Message-ID: <20101128195213.GK14385@redhat.com> References: <20101127170619.GB14385@redhat.com> <20101127174726.GA15238@morn.localdomain> <20101127181541.GC14385@redhat.com> <20101127184012.GA17455@morn.localdomain> <20101127190424.GD14385@redhat.com> <20101127210744.GA21727@morn.localdomain> <20101128074534.GE6897@redhat.com> <20101128171543.GA21987@morn.localdomain> <20101128184734.GE14385@redhat.com> <20101128191145.7688.qmail@stuge.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:3294 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754201Ab0K1Twb (ORCPT ); Sun, 28 Nov 2010 14:52:31 -0500 Content-Disposition: inline In-Reply-To: <20101128191145.7688.qmail@stuge.se> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, Nov 28, 2010 at 08:11:45PM +0100, Peter Stuge wrote: > Peter Stuge wrote: > > Specifying boot device using PCI BDF is a great example of using > > common structured data. That BDF exists both in machine and firmware > > data models. > > Gleb Natapov wrote: > > Bus numbers are assigned by a guest. Qemu knows nothing about them, > > so it specify device path by topology. > > Quite. By BDF I of course mean topology. ;) > Ah, then we are in violent agreement :) > The BDF itself is not much better than a BBS concept, since only the > firmware knows the details. > Yeap. > But the topology is common, even if bus number differs between > machine and firmware. > Correct. > How is the topology structured? I'm not sure that firmware can use a > "slot" number. Device number on the bus works, is that what you mean? > To specify device path to PCI card using topology one needs to specify slot.fn of all pci-to-pci buses from pci host controller to pci device in question. -- Gleb.