qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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] [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind
Date: Mon, 30 Mar 2015 09:28:24 +0800	[thread overview]
Message-ID: <5518A6B8.2050407@intel.com> (raw)
In-Reply-To: <1427450046.13935.90.camel@citrix.com>

On 2015/3/27 17:54, Ian Campbell wrote:
> On Fri, 2015-03-27 at 09:29 +0800, Chen, Tiejun wrote:
>> On 2015/3/26 18:06, Ian Campbell wrote:
>>> On Thu, 2015-03-26 at 08:53 +0800, Chen, Tiejun wrote:
>>>>> Hrm, OK. I suppose we can live with autodetect and igd both meaning igd
>>>>> and whoever adds a new type will have to remember to add a check for
>>>>> qemu-trad then.
>>>>>
>>>>
>>>> When we really have to introduce a new type, this means we probably need
>>>> to change something inside qemu codes. So a new type should just go into
>>>> that table to support qemu upstream since now we shouldn't refactor
>>>> anything in qemu-xen-traditional, right?
>>>
>>> We'd want to error out on attempts to use qemu-xen-trad with non-IGD
>>> passthru.
>>>
>>
>> On qemu-xen-traditional side, we always recognize this as BOOLEAN,
>>
>>           if (libxl_defbool_val(b_info->u.hvm.gfx_passthru)) {
>>
>>               flexarray_append(dm_args, "-gfx_passthru");
>>
>>           }
>>
>> Additionally, this is also clarified explicitly in manpage, and
>> especially we don't change this behavior now, so I'm just wondering why
>> we should do this :)
>
> If someone does gfx_passthru = "foobar" and device_model_version =
> "qemu-xen-traditional" in their xl config then it would be rather mean
> of us to silently enable IGD passthru for them instead. When this occurs
> libxl should notice and fail.
>
> IGD is currently the only option, so this code would be needed when
> someone adds "foobar" support.
>

Sounds it should be a legacy fix to qemu-xen-tranditional :) So lets do 
it now,

@@ -326,6 +326,10 @@ static char ** 
libxl__build_device_model_args_old(libxl__gc *gc,
          }
          if (libxl_defbool_val(b_info->u.hvm.gfx_passthru)) {
              flexarray_append(dm_args, "-gfx_passthru");
+            if (b_info->u.hvm.gfx_passthru_kind >
+                                            LIBXL_GFX_PASSTHRU_KIND_IGD)
+                LOG(ERROR, "unsupported device type for 
\"gfx_passthru\".\n");
+                return NULL;
          }
      } else {
          if (!sdl && !vnc)


Thanks
Tiejun

  reply	other threads:[~2015-03-30  1:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  1:17 [Qemu-devel] [v3][PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream Tiejun Chen
2015-03-23  1:17 ` [Qemu-devel] [v3][PATCH 1/2] libxl: introduce libxl__is_igd_vga_passthru Tiejun Chen
2015-03-23  1:17 ` [Qemu-devel] [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind Tiejun Chen
2015-03-24  8:47   ` [Qemu-devel] One question to lowlevel/xl/xl.c and lowlevel/xc/xc.c Chen, Tiejun
2015-03-24  9:51     ` Ian Campbell
2015-03-24 10:15       ` Chen, Tiejun
2015-03-24 10:20         ` Ian Campbell
2015-03-24 10:31           ` Chen, Tiejun
2015-03-24 10:40             ` Ian Campbell
2015-03-25  1:18               ` Chen, Tiejun
2015-03-25 10:26                 ` Ian Campbell
2015-03-26  0:44                   ` Chen, Tiejun
2015-03-24 14:50   ` [Qemu-devel] [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind Ian Campbell
2015-03-25  1:10     ` Chen, Tiejun
2015-03-25 10:32       ` Ian Campbell
2015-03-26  0:53         ` Chen, Tiejun
2015-03-26 10:06           ` Ian Campbell
2015-03-27  1:29             ` Chen, Tiejun
2015-03-27  9:54               ` Ian Campbell
2015-03-30  1:28                 ` Chen, Tiejun [this message]
2015-03-30  9:19                   ` Ian Campbell
2015-04-01  1:05                     ` Chen, Tiejun
2015-04-01  8:45                       ` Ian Campbell
2015-04-01  9:18                         ` Chen, Tiejun
2015-04-01  9:53                           ` 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=5518A6B8.2050407@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).