From: Ian Campbell <ian.campbell@citrix.com>
To: "Chen, Tiejun" <tiejun.chen@intel.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: Thu, 26 Mar 2015 10:06:58 +0000 [thread overview]
Message-ID: <1427364418.10784.122.camel@citrix.com> (raw)
In-Reply-To: <551358A7.2090607@intel.com>
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.
Ian.
next prev parent reply other threads:[~2015-03-26 10:07 UTC|newest]
Thread overview: 49+ 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 ` [v3][PATCH 1/2] libxl: introduce libxl__is_igd_vga_passthru Tiejun Chen
2015-03-23 1:17 ` [Qemu-devel] " Tiejun Chen
2015-03-23 1:17 ` [Qemu-devel] [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind Tiejun Chen
2015-03-23 1:17 ` 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 9:51 ` [Qemu-devel] " Ian Campbell
2015-03-24 10:15 ` Chen, Tiejun
2015-03-24 10:15 ` [Qemu-devel] " Chen, Tiejun
2015-03-24 10:20 ` Ian Campbell
2015-03-24 10:20 ` [Qemu-devel] " Ian Campbell
2015-03-24 10:31 ` Chen, Tiejun
2015-03-24 10:40 ` Ian Campbell
2015-03-24 10:40 ` [Qemu-devel] " Ian Campbell
2015-03-25 1:18 ` Chen, Tiejun
2015-03-25 1:18 ` [Qemu-devel] " Chen, Tiejun
2015-03-25 10:26 ` Ian Campbell
2015-03-25 10:26 ` [Qemu-devel] " Ian Campbell
2015-03-26 0:44 ` Chen, Tiejun
2015-03-26 0:44 ` Chen, Tiejun
2015-03-24 10:31 ` Chen, Tiejun
2015-03-24 8:47 ` Chen, Tiejun
2015-03-24 14:50 ` [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind Ian Campbell
2015-03-24 14:50 ` [Qemu-devel] " Ian Campbell
2015-03-25 1:10 ` Chen, Tiejun
2015-03-25 1:10 ` [Qemu-devel] " Chen, Tiejun
2015-03-25 10:32 ` Ian Campbell
2015-03-26 0:53 ` Chen, Tiejun
2015-03-26 0:53 ` [Qemu-devel] " Chen, Tiejun
2015-03-26 10:06 ` Ian Campbell [this message]
2015-03-27 1:29 ` Chen, Tiejun
2015-03-27 9:54 ` Ian Campbell
2015-03-30 1:28 ` Chen, Tiejun
2015-03-30 9:19 ` Ian Campbell
2015-03-30 9:19 ` [Qemu-devel] " Ian Campbell
2015-04-01 1:05 ` Chen, Tiejun
2015-04-01 1:05 ` [Qemu-devel] " Chen, Tiejun
2015-04-01 8:45 ` Ian Campbell
2015-04-01 9:18 ` Chen, Tiejun
2015-04-01 9:18 ` [Qemu-devel] " Chen, Tiejun
2015-04-01 9:53 ` Ian Campbell
2015-04-01 9:53 ` [Qemu-devel] " Ian Campbell
2015-04-01 8:45 ` Ian Campbell
2015-03-30 1:28 ` Chen, Tiejun
2015-03-27 9:54 ` Ian Campbell
2015-03-27 1:29 ` Chen, Tiejun
2015-03-26 10:06 ` Ian Campbell
2015-03-25 10:32 ` 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=1427364418.10784.122.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@citrix.com \
--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.