From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=49010 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PMnIK-0004U2-1X
	for qemu-devel@nongnu.org; Sun, 28 Nov 2010 14:52:20 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1PMnII-0002pE-Ro
	for qemu-devel@nongnu.org; Sun, 28 Nov 2010 14:52:19 -0500
Received: from mx1.redhat.com ([209.132.183.28]:57024)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1PMnII-0002ou-K5
	for qemu-devel@nongnu.org; Sun, 28 Nov 2010 14:52:18 -0500
Date: Sun, 28 Nov 2010 21:52:13 +0200
From: Gleb Natapov <gleb@redhat.com>
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
Content-Disposition: inline
In-Reply-To: <20101128191145.7688.qmail@stuge.se>
Subject: [Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org

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.