From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: Source of guest-physical address in PCI BAR for HVM
	domain?
Date: Fri, 4 Jan 2008 16:47:12 +0000
Message-ID: <20080104164712.GK5666@implementation.uk.xensource.com>
References: <1a74a8410801040835t5bb40477u128d310f9d1ed201@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <1a74a8410801040835t5bb40477u128d310f9d1ed201@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: David Stone <unclestoner@gmail.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

David Stone, le Fri 04 Jan 2008 11:35:04 -0500, a écrit :
>   main_loop_wait
>   cpu_handle_ioreq
>   etc.
> So I guess this the PCI config-space write to set the BAR is passed to
> qemu-dm as a command from the hypervisor

Yes.

> this is happending early in the boot process before the guest OS
> proper is even running.  My understanding of how PCI systems work is
> that the BIOS first configures (a subset of) the PCI devices, and
> then the once the real OS is initializing it can re-configure any PCI
> devices it wants to.  Can someone tell me if this is correct?

That's what I remember too.

> If so, shouldn't the early PCI configuration from the BIOS be coming
> from qemu itself?

It is. It's odd you have troubles so early in the boot, is your
configuration a bit special in any way?

Samuel