From: Tiejun Chen <tiejun.chen@intel.com>
To: ian.campbell@citrix.com, wei.liu2@citrix.com,
stefano.stabellini@citrix.com, Ian.Jackson@eu.citrix.com
Cc: qemu-devel@nongnu.org, xen-devel@lists.xen.org
Subject: [Qemu-devel] [v4][PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream
Date: Fri, 18 Sep 2015 16:30:15 +0800 [thread overview]
Message-ID: <1442565017-31725-1-git-send-email-tiejun.chen@intel.com> (raw)
Ian,
As we discussed previously,
http://patchwork.ozlabs.org/patch/457055/
now it's time to push this into on xen/tools side since all qemu stuffs
have been merged.
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg02094.html
v4:
Ian,
Actually we had v3.5 online previously, which was reviewed by you.
http://permalink.gmane.org/gmane.comp.emulators.qemu/329100
So here I just bring a little bit to refine code just for patch #2
according to out last conversation.
v3:
* Refine some codes based on Campbell's feedback so thanks for Campbell's
kind guideline to patch #2
* Update the manpages in patch #2
v2:
* Refine patch #2's head description
* Improve codes quality inside patch #1 based on Wei's comments
* Refill the summary inside patch #0 based on Konrad and Wei's suggestion
When we're working to support IGD GFX passthrough with qemu
upstream, instead of "-gfx_passthru" we'd like to make that
a machine option, "-machine xxx,igd-passthru=on".
https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg02050.html
This need to bring a change on tool side.
After a discussion with Campbell, we'd like to construct a table to record
all IGD devices we can support. If we hit that table, we should pass that
option. And so we also introduce a new field of type, 'gfx_passthru_kind',
to cooperate with 'gfx_passthru' to cover all scenarios like this,
gfx_passthru = 0 => sets build_info.u.gfx_passthru to false
gfx_passthru = 1 => sets build_info.u.gfx_passthru to true and
build_info.u.gfx_passthru_kind to DEFAULT
gfx_passthru = "igd" => sets build_info.u.gfx_passthru to false
and build_info.u.gfx_passthru_kind to IGD
And note actually that option "-gfx_passthru" is just introduced to
work for qemu-xen-traditional so we should get this away from
libxl__build_device_model_args_new() in the case of qemu upstream.
----------------------------------------------------------------
Tiejun Chen (2):
libxl: introduce libxl__is_igd_vga_passthru
libxl: introduce gfx_passthru_kind
docs/man/xl.cfg.pod.5 | 35 ++++++++--
tools/libxl/libxl.h | 6 ++
tools/libxl/libxl_dm.c | 46 +++++++++++--
tools/libxl/libxl_internal.h | 2 +
tools/libxl/libxl_pci.c | 124 +++++++++++++++++++++++++++++++++++
tools/libxl/libxl_types.idl | 6 ++
tools/libxl/xl_cmdimpl.c | 14 +++-
7 files changed, 223 insertions(+), 10 deletions(-)
Thanks
Tiejun
next reply other threads:[~2015-09-18 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 8:30 Tiejun Chen [this message]
2015-09-18 8:30 ` [Qemu-devel] [v4][PATCH 1/2] libxl: introduce libxl__is_igd_vga_passthru Tiejun Chen
2015-09-18 8:30 ` [Qemu-devel] [v4][PATCH 2/2] libxl: introduce gfx_passthru_kind Tiejun Chen
2015-09-25 15:38 ` Ian Campbell
2015-10-06 15:30 ` Stefano Stabellini
2015-09-25 5:51 ` [Qemu-devel] [v4][PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream Chen, Tiejun
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=1442565017-31725-1-git-send-email-tiejun.chen@intel.com \
--to=tiejun.chen@intel.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).