From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: David Stone <unclestoner@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Source of guest-physical address in PCI BAR for HVM domain?
Date: Fri, 4 Jan 2008 18:31:49 +0000 [thread overview]
Message-ID: <20080104183149.GM5666@implementation.uk.xensource.com> (raw)
In-Reply-To: <1a74a8410801041025t66557b3bxd596689e902d4c97@mail.gmail.com>
David Stone, le Fri 04 Jan 2008 13:25:47 -0500, a écrit :
> > > 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.
>
> But doesn't qemu act as the BIOS for HVM domains?
Yes.
> Why would the hypervisor be doing the initial PCI BAR setup?
The hypervisor does nothing but retransmit what the HVM domain performs.
Remember that instructions of the qemu BIOS are run in the HVM domain,
not in qemu, which only gets triggered when the BIOS actually I/O ports
or memory.
> > > 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?
>
> Yes, I didn't mention the most important part: the device in question
> is a physical PCI device (a PCI Express graphics card) that I am
> passing through to the Windows 2003 guest domain via VT-d. (The VT-d
> support generally works for me because I can pass a PCI NIC through no
> problem.) (I realize VT-d'ing a PCI-XP graphics card is
> experimental...but that's what I'm doing, experimenting...).
Then maybe the qemu BIOS has troubles with that device?
Samuel
next prev parent reply other threads:[~2008-01-04 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 16:35 Source of guest-physical address in PCI BAR for HVM domain? David Stone
2008-01-04 16:47 ` Samuel Thibault
2008-01-04 18:25 ` David Stone
2008-01-04 18:31 ` Samuel Thibault [this message]
2008-01-04 22:30 ` David Stone
2008-01-06 23:15 ` Keir Fraser
2008-01-07 21:39 ` David Stone
2008-01-07 21:43 ` Keir Fraser
2008-01-07 23:46 ` Source of guest-physical address in PCI BAR for HVMdomain? Zulauf, John
2008-01-08 2:13 ` Alan Cox
2008-01-08 8:19 ` Keir Fraser
2008-01-08 21:51 ` David Stone
2008-01-10 22:46 ` Zulauf, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080104183149.GM5666@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=unclestoner@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.