From: Jean Guyader <jean.guyader@citrix.com>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
"Lin, Ben Y" <ben.y.lin@intel.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
Fraser <Keir.Fraser@eu.citrix.com>Keir,
"'bengheng@eecs.umich.edu'" <bengheng@eecs.umich.edu>
Subject: Re: [PATCH 1/2] graphics passthrough with VT-d
Date: Fri, 28 Aug 2009 09:12:32 +0100 [thread overview]
Message-ID: <20090828081232.GA14065@citrix.com> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C054B533682@pdsmsx503.ccr.corp.intel.com>
On Fri, Aug 28, 2009 at 03:54:05AM -0400, Han, Weidong wrote:
> This patch supports basic gfx passthrough on xen side:
> - retrieves VGA bios from host VGA BIOS address (0xC0000), then load it to guest VGA BIOS address (This is the same with XCI).
> - Enlarge guest MMIO range to contain gfx card's large memory
> - add a config option 'gfx_passthru' for gfx passthrough
>
> Signed-off-by: Ben Lin <ben.y.lin@intel.com>
> Signed-off-by: Weidong Han <weidong.han@intel.com>
Hi,
First thanks for taking the time to upstream those patch
that will help a lot.
I think the patch will be let intrusive if we could do all
that bios mapping + copying inside qemu so we don't need to
modify the xc_hvm_build function.
Qemu starts before the bios so that should be doable.
Thanks,
Jean
next prev parent reply other threads:[~2009-08-28 8:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 7:54 [PATCH 1/2] graphics passthrough with VT-d Han, Weidong
2009-08-28 8:12 ` Jean Guyader [this message]
2009-08-28 8:30 ` Han, Weidong
2009-09-11 15:41 ` Stefano Stabellini
2009-09-16 5:10 ` Han, Weidong
2009-09-16 8:33 ` Jean Guyader
2009-09-16 8:54 ` Han, Weidong
2009-09-16 10:57 ` Stefano Stabellini
2009-09-17 11:11 ` Han, Weidong
2009-09-18 7:42 ` Han, Weidong
2009-09-19 1:15 ` Stefano Stabellini
2009-09-20 12:59 ` Han, Weidong
2009-09-20 16:49 ` Stefano Stabellini
2009-08-28 8:45 ` Keir Fraser
2009-08-28 8:46 ` Han, Weidong
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=20090828081232.GA14065@citrix.com \
--to=jean.guyader@citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=allen.m.kay@intel.com \
--cc=ben.y.lin@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 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.