xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Han, Weidong" <weidong.han@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"Kay, Allen M" <allen.m.kay@intel.com>
Subject: Re: [PATCH 0/3] VT-d: support Intel IGD passthrough
Date: Thu, 04 Feb 2010 08:24:37 +0000	[thread overview]
Message-ID: <C79034C5.8FAA%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <60E426D47DE8EA47AA104E65008A100D1621AFC6F3@shzsmsx501.ccr.corp.intel.com>

Cc'ing Ian Jackson for applying patch 1/3. And I didn't receive your patch
2/3. I've received and will apply your patch 3/3 however.

 -- Keir

On 04/02/2010 08:12, "Han, Weidong" <weidong.han@intel.com> wrote:

> The patchset supports Intel IGD passthrough in Xen. There are some
> assumptions/dependencies on chipset, VBIOS, and even drivers for IGD. But
> virtual platform is not aware of it. This patchset handles it to make IGD work
> in guest. What's more, FLR capability of IGD is not exposed on some platforms,
> this patchset uses vendor specific FLR to reset those IGDs.
> 
> Also add an option into hvm config file to enable graphics passthrough.
> 
> The patchset was tested in Intel McCreary platform, guest WinXP, Win7 and
> Linux all worked.
> 
> Patch 1: qemu-igd.patch:
> Some registers of Intel IGD are mapped in host bridge, so it needs to
> passthrough these registers of physical host bridge to guest because emulated
> host bridge in guest doesn't have these mappings.
> Some VBIOSs and drivers assume the IGD BDF (bus:device:function) is always
> 00:02.0, so this patch reserves 00:02.0 for assigned IGD in guest.
> 
> Patch 2: igd-flr.patch:
> Due to FLR capability of IGD is not exposed on some platforms, this patch uses
> vendor specific FLR to reset those IGDs.
> 
> Patch 3: gfx-conf.patch:
> The patch adds an option into hvm config file to enable graphics passthrough
> including discrete and IGD. To passthrough graphics to guest, need to set
> gfx_passthru=1, and also specify graphics device BDF in pci passthrough
> option, like pci=['xx:xx.x'] in hvm config file.
> 
> 
> Signed-off-by: Weidong Han <weidong.han@intel.com>

  reply	other threads:[~2010-02-04  8:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04  8:12 [PATCH 0/3] VT-d: support Intel IGD passthrough Han, Weidong
2010-02-04  8:24 ` Keir Fraser [this message]
2010-02-04  8:29   ` Han, Weidong
2010-02-04 12:15 ` Christian Tramnitz
2010-02-05  2:11   ` Han, Weidong
2010-02-06 12:51     ` Andrew Lyon
2010-02-08  3:27       ` Weidong Han
2010-02-13 12:52         ` Sander Eikelenboom

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=C79034C5.8FAA%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=allen.m.kay@intel.com \
    --cc=weidong.han@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).