From: Peter Stuge Subject: Re: [SeaBIOS] [PATCHv6 00/16] boot order specification Date: Sun, 28 Nov 2010 20:11:45 +0100 Message-ID: <20101128191145.7688.qmail@stuge.se> References: <20101127164939.GA13605@morn.localdomain> <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> 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 foo.birdnet.se ([213.88.146.6]:36300 "HELO foo.stuge.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753866Ab0K1TLr (ORCPT ); Sun, 28 Nov 2010 14:11:47 -0500 Content-Disposition: inline In-Reply-To: <20101128190029.6136.qmail@stuge.se> <20101128184734.GE14385@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. ;) The BDF itself is not much better than a BBS concept, since only the firmware knows the details. But the topology is common, even if bus number differs between machine and firmware. 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? //Peter