From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian.Jackson@eu.citrix.com, wei.liu2@citrix.com,
qemu-devel@nongnu.org, stefano.stabellini@citrix.com,
xen-devel@lists.xen.org
Subject: Re: [Qemu-devel] [v2][PATCH 2/2] libxl: introduce gfx_passthru_kind
Date: Tue, 17 Mar 2015 15:46:30 +0800 [thread overview]
Message-ID: <5507DBD6.8030401@intel.com> (raw)
In-Reply-To: <1426508400.18247.33.camel@citrix.com>
>>> If I remember the context correctly this is in the autodetect case,
>>> so I think shouldn't mention IGD. Something like "Unable to detect
>>> graphics passthru kind, please set gfx_passthru_kind. See xl.cfg(5)
>>> for more
>>
>> s/gfx_passthru_kind/gfx_passthru, right? Because actually we always get
>> 'gfx_passthru_kind' from 'gfx_passthru'.
>
> I think you have it backwards.
>
> In the case here gfx_passthru=1 has been set by the user, but
> gfx_passthru_kind=DEFAULT. So libxl has tried to autodetect but it has
> failed.
>
> So if the user wants to make progress they should set gfx_passthru_kind
> to whatever type of passthrough they were trying to do.
Looks you're saying 'gfx_passthru_kind' shouldn't reply on
'gfx_passthru', so 'gfx_passthru_kind' can override that previous value
parsed from 'gfx_passthru', right?
>
> Alternatively I suppose you could recommend removing gfx_passthru=1 (or
I'm still keep that currently.
> changing to=0), but given they've set =1 that doesn't seem to be the
> most productive suggestion.
>
So looks the whole policy should be something like this,
diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
index 5c40e84..5518759 100644
--- a/tools/libxl/xl_cmdimpl.c
+++ b/tools/libxl/xl_cmdimpl.c
@@ -1953,8 +1953,27 @@ skip_vfb:
xlu_cfg_replace_string (config, "spice_streaming_video",
&b_info->u.hvm.spice.streaming_video, 0);
xlu_cfg_get_defbool(config, "nographic",
&b_info->u.hvm.nographic, 0);
- xlu_cfg_get_defbool(config, "gfx_passthru",
- &b_info->u.hvm.gfx_passthru, 0);
+ if (!xlu_cfg_get_long(config, "gfx_passthru", &l, 1)) {
+ libxl_defbool_set(&b_info->u.hvm.gfx_passthru, l);
+ } else if (!xlu_cfg_get_string(config, "gfx_passthru", &buf, 0)) {
+ if (libxl_gfx_passthru_kind_from_string(buf,
+
&b_info->u.hvm.gfx_passthru_kind)) {
+ fprintf(stderr,
+ "ERROR: invalid value \"%s\" for
\"gfx_passthru\"\n",
+ buf);
+ exit (1);
+ }
+ libxl_defbool_set(&b_info->u.hvm.gfx_passthru, true);
+ }
+ if (!xlu_cfg_get_string(config, "gfx_passthru_kind", &buf, 0)) {
+ if (libxl_gfx_passthru_kind_from_string(buf,
+
&b_info->u.hvm.gfx_passthru_kind)) {
+ fprintf(stderr,
+ "ERROR: invalid value \"%s\" for
\"gfx_passthru_kind\"\n",
+ buf);
+ exit (1);
+ }
+ }
switch (xlu_cfg_get_list_as_string_list(config, "serial",
&b_info->u.hvm.serial_list,
1))
Thanks
Tiejun
next prev parent reply other threads:[~2015-03-17 7:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 9:42 [Qemu-devel] [v2][PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream Tiejun Chen
2015-03-10 9:42 ` [Qemu-devel] [v2][PATCH 1/2] libxl: introduce libxl__is_igd_vga_passthru Tiejun Chen
2015-03-11 11:26 ` Ian Campbell
2015-03-10 9:42 ` [Qemu-devel] [v2][PATCH 2/2] libxl: introduce gfx_passthru_kind Tiejun Chen
2015-03-11 11:34 ` Ian Campbell
2015-03-12 3:18 ` Chen, Tiejun
2015-03-12 12:26 ` Ian Campbell
2015-03-13 1:39 ` Chen, Tiejun
2015-03-13 10:11 ` Ian Campbell
2015-03-16 1:07 ` Chen, Tiejun
2015-03-16 12:20 ` Ian Campbell
2015-03-17 7:46 ` Chen, Tiejun [this message]
2015-03-17 9:26 ` Ian Campbell
2015-03-18 7:32 ` Chen, Tiejun
2015-03-18 10:25 ` Ian Campbell
2015-03-19 2:07 ` Chen, Tiejun
2015-03-19 10:44 ` Ian Campbell
2015-03-20 1:04 ` Chen, Tiejun
2015-03-20 9:40 ` Ian Campbell
2015-03-20 10:08 ` Chen, Tiejun
2015-03-20 10:11 ` Ian Campbell
2015-03-20 10:20 ` 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=5507DBD6.8030401@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).