qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: qemu-devel@nongnu.org, stefano.stabellini@citrix.com,
	Ian.Jackson@eu.citrix.com, ian.campbell@citrix.com,
	xen-devel@lists.xen.org
Subject: Re: [Qemu-devel] [PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream
Date: Mon, 09 Mar 2015 13:32:08 +0800	[thread overview]
Message-ID: <54FD3058.6030309@intel.com> (raw)
In-Reply-To: <20150306122846.GN12103@zion.uk.xensource.com>

On 2015/3/6 20:28, Wei Liu wrote:
> On Fri, Mar 06, 2015 at 05:08:21PM +0800, Tiejun Chen wrote:
>> 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". 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 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
>>
>> ----------------------------------------------------------------
>> Tiejun Chen (2):
>>        libxl: introduce libxl__is_igd_vga_passthru
>>        libxl: introduce gfx_passthru_kind
>>
>>   tools/libxl/libxl_dm.c       |  13 +++++++++++++
>>   tools/libxl/libxl_internal.h |   2 ++
>>   tools/libxl/libxl_pci.c      | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> It might be helpful to use --stat-width=72 or some other options to
> limit the width of your diffstat. :-)
>

Will do.

Thanks
Tiejun

  reply	other threads:[~2015-03-09  5:32 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
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 [this message]
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=54FD3058.6030309@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).