From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
ian.jackson@eu.citrix.com, wei.liu2@citrix.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2 2/2] tools: Do not expose all builds to unstable hypercall APIs by default
Date: Wed, 3 Feb 2016 17:09:43 +0000 [thread overview]
Message-ID: <56B23457.6070500@citrix.com> (raw)
In-Reply-To: <1454515849-13886-2-git-send-email-ian.campbell@citrix.com>
On 03/02/16 16:10, Ian Campbell wrote:
> Currently __XEN_TOOLS__ is defined in the global CFLAGS used for tools
> builds, exposing them all to the various unstable hypercall interfaces.
>
> However there are places where we do not want this (in particular all
> the stable libraries now under tools/libs), and there is a risk of
> such uses slipping in unnoticed (currently there are none, but I
> tripped over the mixed nature of the HVMOPs just now in some new code
> I was putting together).
>
> Instead only define __XEN_TOOLS__ for things which explicitly want the
> unstable APIs. The vast majority of these are consumers of libxenctrl,
> which have opted into unstable interfaces by using libxenctrl already,
> so adding -D__XEN_TOOLS__ to CFLAGS_libxenctrl covers these without
> needing to patch the dozen or so tools manually.
>
> The libxc build itself, which doesn't use CFLAGS_libxenctrl, now needs
> the define too. As does gdbsx's own low level hypercall binding
> library xg.
>
> hvmloader no longer needs to undefine the symbol.
>
> The ocaml evtchn bindings don't actually need sysctl.h and therefore
> don't actually need __XEN_TOOLS__ either.
>
> qemu-xen-traditional doesn't use CFLAGS_libxenctrl and so we pass the
> define there (via --extra-cflags) too.
>
> Having removed __XEN_TOOLS__ replace it with
> __XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ so that in
> tree code is always using the latest APIs.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com> for the x86 bits.
next prev parent reply other threads:[~2016-02-03 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 16:10 [PATCH v2 1/2] tools: consolidate Makefile runes to building+installing qemu-trad Ian Campbell
2016-02-03 16:10 ` [PATCH v2 2/2] tools: Do not expose all builds to unstable hypercall APIs by default Ian Campbell
2016-02-03 16:13 ` Ian Jackson
2016-02-03 17:09 ` Andrew Cooper [this message]
2016-02-03 16:12 ` [PATCH v2 1/2] tools: consolidate Makefile runes to building+installing qemu-trad Ian Jackson
2016-02-04 16:20 ` 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=56B23457.6070500@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.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).