qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	ian.campbell@citrix.com
Cc: wei.liu2@citrix.com, qemu-devel@nongnu.org, xen-devel@lists.xen.org
Subject: Re: [Qemu-devel] [RFC][PATCH 1/1] libxl: add one machine property to support IGD GFX passthrough
Date: Mon, 26 Jan 2015 08:44:34 +0800	[thread overview]
Message-ID: <54C58DF2.2090509@intel.com> (raw)
In-Reply-To: <54C19936.1060804@intel.com>

On 2015/1/23 8:43, Chen, Tiejun wrote:
> On 2015/1/22 8:51, Chen, Tiejun wrote:
>> On 2015/1/21 21:48, Gerd Hoffmann wrote:
>>> On Mi, 2015-01-21 at 11:37 +0000, Ian Jackson wrote:
>>>> Tiejun Chen writes ("[RFC][PATCH 1/1] libxl: add one machine property
>>>> to support IGD GFX passthrough"):
>>>>> 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.
>>>>
>>>> Has the corresponding patch to qemu-upstream been accepted yet ?
>>>>
>>>> I'd like to see a confirmation from the qemu side that this is going
>>>> into their tree and that the command-line option syntax has been
>>>> agreed.
>>>
>>> Suggested at patch review, not merged (guess thats why it is tagged
>>> 'rfc', to get both qemu+xen on the same page).
>>
>> Yeah, this is exactly what I intended to do here :)
>>
>>>
>>> While being at it:  Should we name this 'igd-passthru' instead of
>>> 'gfx-passthru'?  The hostbridge / isabridge quirks needed are actually
>>> specific to igd and are not needed for -- say -- nvidia gfx cards.
>>>
>>
>> At this point I just concern here if we still use 'gfx_passthrou', at
>> least it may look like a backward compatibility with older versions of
>> qemu in Xen side, qemu-xen-traditional. But I'd like to follow your
>> final option.
>>
>
> Any feedback to this option I should follow here?
>

Ping...

Thanks
Tiejun

  reply	other threads:[~2015-01-26  0:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  7:19 [Qemu-devel] [RFC][PATCH 1/1] libxl: add one machine property to support IGD GFX passthrough Tiejun Chen
2015-01-21  7:26 ` 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 [this message]
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=54C58DF2.2090509@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@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).