From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: stefano.stabellini@citrix.com, xen-devel@lists.xen.org,
Ian.Jackson@eu.citrix.com, ian.campbell@citrix.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] libxl: introduce gfx_passthru_kind
Date: Mon, 09 Mar 2015 14:50:42 +0800 [thread overview]
Message-ID: <54FD42C2.60509@intel.com> (raw)
In-Reply-To: <20150306125902.GQ12103@zion.uk.xensource.com>
On 2015/3/6 20:59, Wei Liu wrote:
> On Fri, Mar 06, 2015 at 05:18:36PM +0800, Chen, Tiejun wrote:
>> On 2015/3/6 17:08, Tiejun Chen wrote:
>>> Although we already have 'gfx_passthru' in b_info, this doesn' suffice
>>> after we want to handle IGD specifically. Now we define a new field of
>>> type, gfx_passthru_kind, to indicate we're trying to pass IGD. Actually
>>> this means we can benefit this to support other specific devices just
>>> by extending gfx_passthru_kind. And then we can cooperate with
>>> gfx_passthru to address IGD cases as follows:
>>>
>>> gfx_passthru = 0 => sets build_info.u.gfx_passthru to false
>>> gfx_passthru = 1 => sets build_info.u.gfx_passthru to false 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
>>>
>>> Here if gfx_passthru_kind = DEFAULT, we will call
>>> libxl__is_igd_vga_passthru() to check if we're hitting that table to need
>>> to pass that option to qemu. But if gfx_passthru_kind = "igd" we always
>>> force to pass that.
>>>
>>> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
>>> ---
>>> tools/libxl/libxl_dm.c | 13 +++++++++++++
>>> tools/libxl/libxl_types.idl | 6 ++++++
>>> tools/libxl/xl_cmdimpl.c | 19 +++++++++++++++++--
>>> 3 files changed, 36 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
>>> index 8599a6a..780dd2a 100644
>>> --- a/tools/libxl/libxl_dm.c
>>> +++ b/tools/libxl/libxl_dm.c
>>
>> Sorry, looks I'm missing to remove '-gfx_passthru' since this should be gone
>> in the case of qemu upstream,
>>
>> @@ -710,9 +710,6 @@ static char **
>> libxl__build_device_model_args_new(libxl__gc *gc,
>> flexarray_append(dm_args, "-net");
>> flexarray_append(dm_args, "none");
>> }
>> - if (libxl_defbool_val(b_info->u.hvm.gfx_passthru)) {
>> - flexarray_append(dm_args, "-gfx_passthru");
>> - }
>> } else {
>> if (!sdl && !vnc) {
>> flexarray_append(dm_args, "-nographic");
>>
>> I will fold this into next revision after this review.
>>
>
> I think this change alone warrants a separate changeset. It should be
> patch 0 of your series as a preparatory patch. Please remember to
> elaborate in commit message why that hunk is not needed in upstream
> QEMU.
>
What about this?
"-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.
Thanks
Tiejun
next prev parent reply other threads:[~2015-03-09 6:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 9:08 [Qemu-devel] [PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream Tiejun Chen
2015-03-06 9:08 ` [Qemu-devel] [PATCH 1/2] libxl: introduce libxl__is_igd_vga_passthru Tiejun Chen
2015-03-06 12:40 ` Wei Liu
2015-03-09 6:27 ` Chen, Tiejun
2015-03-09 10:12 ` Wei Liu
2015-03-06 9:08 ` [Qemu-devel] [PATCH 2/2] libxl: introduce gfx_passthru_kind Tiejun Chen
2015-03-06 9:18 ` Chen, Tiejun
2015-03-06 12:59 ` Wei Liu
2015-03-09 6:50 ` Chen, Tiejun [this message]
2015-03-09 10:13 ` Wei Liu
2015-03-06 12:55 ` Wei Liu
2015-03-09 6:45 ` Chen, Tiejun
2015-03-09 10:17 ` Wei Liu
2015-03-10 0:28 ` Chen, Tiejun
2015-03-11 11:23 ` Ian Campbell
2015-03-06 12:28 ` [Qemu-devel] [PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream Wei Liu
2015-03-09 5:32 ` Chen, Tiejun
2015-03-06 15:53 ` [Qemu-devel] [Xen-devel] " Konrad Rzeszutek Wilk
2015-03-09 6:58 ` 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=54FD42C2.60509@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).