All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: qemu-devel@nongnu.org, Tiejun Chen <tiejun.chen@intel.com>,
	wei.liu2@citrix.com, kraxel@redhat.com, xen-devel@lists.xen.org
Subject: Re: [Qemu-devel] [RFC][PATCH 1/1] libxl: add one machine property to support IGD GFX passthrough
Date: Wed, 21 Jan 2015 11:56:16 +0000	[thread overview]
Message-ID: <1421841376.13271.5.camel@citrix.com> (raw)
In-Reply-To: <21695.36752.122911.770104@mariner.uk.xensource.com>

On Wed, 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.

Do we need to detect old vs. new qemu to know when this option is valid?

Ian.

  parent reply	other threads:[~2015-01-21 11:56 UTC|newest]

Thread overview: 39+ 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  7:26 ` Chen, Tiejun
2015-01-21 11:37 ` Ian Jackson
2015-01-21 11:37 ` [Qemu-devel] " Ian Jackson
2015-01-21 11:56   ` Ian Campbell
2015-01-21 11:56   ` Ian Campbell [this message]
2015-01-22  0:55     ` [Qemu-devel] " Chen, Tiejun
2015-01-22  0:55     ` Chen, Tiejun
2015-01-21 13:48   ` [Qemu-devel] " Gerd Hoffmann
2015-01-22  0:51     ` Chen, Tiejun
2015-01-22  0:51     ` [Qemu-devel] " Chen, Tiejun
2015-01-23  0:43       ` Chen, Tiejun
2015-01-23  0:43       ` Chen, Tiejun
2015-01-26  0:44         ` Chen, Tiejun
2015-01-27 14:40           ` Ian Jackson
2015-01-28  0:42             ` Chen, Tiejun
2015-01-28 11:12               ` Wei Liu
2015-01-28 11:12               ` Wei Liu
2015-01-29  0:41                 ` Chen, Tiejun
2015-01-29  0:41                 ` Chen, Tiejun
2015-01-29 10:50                   ` Wei Liu
2015-01-29 10:50                   ` Wei Liu
2015-01-30  0:56                     ` Chen, Tiejun
2015-01-30 12:26                       ` Wei Liu
2015-01-30 12:26                       ` Wei Liu
2015-01-31  7:07                         ` [Qemu-devel] [Xen-devel] " Xu, Quan
2015-01-31 14:33                           ` [Qemu-devel] " Wei Liu
2015-01-31 14:33                           ` [Qemu-devel] [Xen-devel] " Wei Liu
2015-01-31 15:21                             ` Xu, Quan
2015-01-31 15:21                             ` [Qemu-devel] " Xu, Quan
2015-01-31  7:07                         ` Xu, Quan
2015-02-02  0:43                         ` Chen, Tiejun
2015-02-02  0:43                         ` Chen, Tiejun
2015-01-30  0:56                     ` Chen, Tiejun
2015-01-28  0:42             ` Chen, Tiejun
2015-01-27 14:40           ` Ian Jackson
2015-01-26  0:44         ` Chen, Tiejun
2015-01-21 13:48   ` Gerd Hoffmann

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=1421841376.13271.5.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tiejun.chen@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.