From: Tiejun Chen <tiejun.chen@intel.com>
To: ian.jackson@eu.citrix.com, ian.campbell@citrix.com, wei.liu2@citrix.com
Cc: qemu-devel@nongnu.org, kraxel@redhat.com, xen-devel@lists.xen.org
Subject: [Qemu-devel] [RFC][PATCH 1/1] libxl: add one machine property to support IGD GFX passthrough
Date: Wed, 21 Jan 2015 15:19:52 +0800 [thread overview]
Message-ID: <1421824792-3925-1-git-send-email-tiejun.chen@intel.com> (raw)
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,gfx_passthru=on". This need
to bring several changes on tool side.
Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
---
tools/libxl/libxl_dm.c | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
index c2b0487..2b59d2c 100644
--- a/tools/libxl/libxl_dm.c
+++ b/tools/libxl/libxl_dm.c
@@ -318,7 +318,10 @@ static char ** libxl__build_device_model_args_old(libxl__gc *gc,
flexarray_vappend(dm_args, "-net", "none", NULL);
}
if (libxl_defbool_val(b_info->u.hvm.gfx_passthru)) {
- flexarray_append(dm_args, "-gfx_passthru");
+ if (b_info->device_model_version !=
+ LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN) {
+ flexarray_append(dm_args, "-gfx_passthru");
+ }
}
} else {
if (!sdl && !vnc)
@@ -702,7 +705,10 @@ static char ** libxl__build_device_model_args_new(libxl__gc *gc,
flexarray_append(dm_args, "none");
}
if (libxl_defbool_val(b_info->u.hvm.gfx_passthru)) {
- flexarray_append(dm_args, "-gfx_passthru");
+ if (b_info->device_model_version !=
+ LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN) {
+ flexarray_append(dm_args, "-gfx_passthru");
+ }
}
} else {
if (!sdl && !vnc) {
@@ -748,6 +754,15 @@ static char ** libxl__build_device_model_args_new(libxl__gc *gc,
machinearg, max_ram_below_4g);
}
}
+
+ if (b_info->device_model_version ==
+ LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN) {
+ if (libxl_defbool_val(b_info->u.hvm.gfx_passthru)) {
+ machinearg = libxl__sprintf(gc, "%s,gfx_passthru=on",
+ machinearg);
+ }
+ }
+
flexarray_append(dm_args, machinearg);
for (i = 0; b_info->extra_hvm && b_info->extra_hvm[i] != NULL; i++)
flexarray_append(dm_args, b_info->extra_hvm[i]);
--
1.9.1
next reply other threads:[~2015-01-21 7:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 7:19 Tiejun Chen [this message]
2015-01-21 7:26 ` [Qemu-devel] [RFC][PATCH 1/1] libxl: add one machine property to support IGD GFX passthrough Chen, Tiejun
2015-01-21 11:37 ` Ian Jackson
2015-01-21 11:56 ` Ian Campbell
2015-01-22 0:55 ` Chen, Tiejun
2015-01-21 13:48 ` Gerd Hoffmann
2015-01-22 0:51 ` Chen, Tiejun
2015-01-23 0:43 ` Chen, Tiejun
2015-01-26 0:44 ` Chen, Tiejun
2015-01-27 14:40 ` Ian Jackson
2015-01-28 0:42 ` Chen, Tiejun
2015-01-28 11:12 ` Wei Liu
2015-01-29 0:41 ` Chen, Tiejun
2015-01-29 10:50 ` Wei Liu
2015-01-30 0:56 ` Chen, Tiejun
2015-01-30 12:26 ` Wei Liu
2015-01-31 7:07 ` [Qemu-devel] [Xen-devel] " Xu, Quan
2015-01-31 14:33 ` Wei Liu
2015-01-31 15:21 ` Xu, Quan
2015-02-02 0:43 ` [Qemu-devel] " 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=1421824792-3925-1-git-send-email-tiejun.chen@intel.com \
--to=tiejun.chen@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).