From: Ian Campbell <Ian.Campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: wei.liu2@citrix.com, vijay.kilari@gmail.com,
stefano.stabellini@eu.citrix.com, tim@xen.org,
Vijaya.Kumar@caviumnetworks.com,
Julien Grall <julien.grall@linaro.org>,
ian.jackson@eu.citrix.com, stefano.stabellini@citrix.com,
Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xenproject.org, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v2 for 4.5] xen/arm: Add support for GICv3 for domU
Date: Mon, 10 Nov 2014 10:03:03 +0000 [thread overview]
Message-ID: <1415613783.27002.2.camel@citrix.com> (raw)
In-Reply-To: <7EFC68C5-25FF-47E8-83B3-0600246D8937@oracle.com>
On Sat, 2014-11-08 at 15:26 -0500, Konrad Rzeszutek Wilk wrote:
> That is to guard against somebody building against libxc or libxl and
> then becoming dependent on this and then complaining that it is not in
> Xen 4.6.
libxc does not have a stable API and libxl doesn't expose this interface
at all. At the hypercall level this is a domctl which simliarly has no
stable interface.
So I don't think there is any need to wrap anything or guard against
anything.
next prev parent reply other threads:[~2014-11-10 10:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 20:10 [PATCH v2 for 4.5] xen/arm: Add support for GICv3 for domU Julien Grall
2014-11-03 11:01 ` Stefano Stabellini
2014-11-03 12:37 ` Vijay Kilari
2014-11-03 16:39 ` Konrad Rzeszutek Wilk
2014-11-04 17:26 ` Julien Grall
2014-11-05 10:25 ` Ian Campbell
2014-11-05 17:15 ` Jan Beulich
2014-11-06 9:45 ` Julien Grall
2014-11-06 10:11 ` Jan Beulich
2014-11-06 10:27 ` Julien Grall
2014-11-07 15:45 ` Konrad Rzeszutek Wilk
2014-11-08 18:01 ` Julien Grall
2014-11-08 20:26 ` Konrad Rzeszutek Wilk
2014-11-10 10:03 ` Ian Campbell [this message]
2014-11-10 11:38 ` Stefano Stabellini
2014-11-11 16:41 ` Julien Grall
2014-11-11 16:43 ` Stefano Stabellini
2014-11-11 17:10 ` Konrad Rzeszutek Wilk
2014-11-03 22:51 ` Daniel De Graaf
2014-11-05 10:24 ` Ian Campbell
2014-11-05 10:31 ` Stefano Stabellini
2014-11-05 10:56 ` Ian Campbell
2014-11-05 11:02 ` Stefano Stabellini
2014-11-05 11:20 ` Ian Campbell
2014-11-05 11:10 ` Julien Grall
2014-11-05 11:22 ` Ian Campbell
2014-11-05 11:28 ` Julien Grall
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=1415613783.27002.2.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=vijay.kilari@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.