From: Yang Zhang <yang.z.zhang@intel.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, xen-devel@lists.xensource.com,
stefano.stabellini@eu.citrix.com, allen.m.kay@intel.com,
weidong.han@intel.com, jean.guyader@eu.citrix.com,
Yang Zhang <yang.z.zhang@Intel.com>,
anthony@codemonkey.ws, anthony.perard@citrix.com
Subject: [Qemu-devel] [PATCH 0/5] xen: add Intel IGD passthrough support
Date: Fri, 21 Feb 2014 14:44:08 +0800 [thread overview]
Message-ID: <1392965053-1069-1-git-send-email-yang.z.zhang@intel.com> (raw)
From: Yang Zhang <yang.z.zhang@Intel.com>
The following patches are ported from Xen Qemu-traditional branch which are
adding Intel IGD passthrough supporting to Qemu upstream.
To pass through IGD to guest, user need to add following lines in Xen config
file:
gfx_passthru=1
pci=['00:02.0@2']
Besides, since Xen + Qemu upstream is requiring seabios, user also need to
recompile seabios with CONFIG_OPTIONROMS_DEPLOYED=y to allow IGD pass through
successfully:
1. change CONFIG_OPTIONROMS_DEPLOYED=y in file: xen/tools/firmware/seabios-config
2. recompile the tools
I have successfully boot Win 7 and RHEL6u4 guests with IGD assigned in Haswell
desktop with Latest Xen + Qemu upstream.
Yang Zhang (5):
xen, gfx passthrough: basic graphics passthrough support
xen, gfx passthrough: reserve 00:02.0 for INTEL IGD
xen, gfx passthrough: create intel isa bridge
xen, gfx passthrough: support Intel IGD passthrough with VT-D
xen, gfx passthrough: add opregion mapping
configure | 2 +-
hw/pci-host/piix.c | 15 ++
hw/pci/pci.c | 19 ++
hw/xen/Makefile.objs | 2 +-
hw/xen/xen-host-pci-device.c | 5 +
hw/xen/xen-host-pci-device.h | 1 +
hw/xen/xen_pt.c | 10 +
hw/xen/xen_pt.h | 13 ++-
hw/xen/xen_pt_config_init.c | 45 +++++-
hw/xen/xen_pt_graphics.c | 407 ++++++++++++++++++++++++++++++++++++++++++
qemu-options.hx | 9 +
vl.c | 8 +
12 files changed, 532 insertions(+), 4 deletions(-)
create mode 100644 hw/xen/xen_pt_graphics.c
next reply other threads:[~2014-02-21 6:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:44 Yang Zhang [this message]
2014-02-21 6:44 ` [Qemu-devel] [PATCH 1/5] xen, gfx passthrough: basic graphics passthrough support Yang Zhang
2014-03-21 16:24 ` Anthony PERARD
2014-05-09 7:27 ` Zhang, Yang Z
2014-04-02 15:19 ` [Qemu-devel] [Xen-devel] " Zytaruk, Kelly
2014-02-21 6:44 ` [Qemu-devel] [PATCH 2/5] xen, gfx passthrough: reserve 00:02.0 for INTEL IGD Yang Zhang
2014-03-21 17:26 ` Anthony PERARD
2014-02-21 6:44 ` [Qemu-devel] [PATCH 3/5] xen, gfx passthrough: create intel isa bridge Yang Zhang
2014-02-21 6:44 ` [Qemu-devel] [PATCH 4/5] xen, gfx passthrough: support Intel IGD passthrough with VT-D Yang Zhang
2014-03-27 18:21 ` Stefano Stabellini
2014-03-27 19:10 ` Michael S. Tsirkin
2014-02-21 6:44 ` [Qemu-devel] [PATCH 5/5] xen, gfx passthrough: add opregion mapping Yang Zhang
2014-02-27 5:38 ` [Qemu-devel] [PATCH 0/5] xen: add Intel IGD passthrough support Zhang, Yang Z
2014-02-27 12:47 ` Stefano Stabellini
2014-04-04 22:46 ` Kevin O'Connor
2014-04-07 8:36 ` [Qemu-devel] [Xen-devel] " Ian Campbell
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=1392965053-1069-1-git-send-email-yang.z.zhang@intel.com \
--to=yang.z.zhang@intel.com \
--cc=allen.m.kay@intel.com \
--cc=anthony.perard@citrix.com \
--cc=anthony@codemonkey.ws \
--cc=jean.guyader@eu.citrix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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).