From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>, Tim Deegan <tim@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH for-4.5] xen: Bump several interface versions in preparation for Xen-4.5
Date: Tue, 4 Nov 2014 11:46:49 +0000 [thread overview]
Message-ID: <5458BCA9.3000304@citrix.com> (raw)
In-Reply-To: <1415101481-23913-1-git-send-email-andrew.cooper3@citrix.com>
On 04/11/14 11:44, Andrew Cooper wrote:
Apologies - the subject is wrong, but content is correct. (I think,
having now checked the other interface versions).
> c/s fce5281c "x86/mem_access: Deprecate the HVM mem_access ops" removes the
> structures associated with xen_hvm_{get,set}_mem_access from the Xen public
> API.
>
> While these were toolstack hypercalls and documented as liable to change in
> the future, it causes build issues for certain tools (valgrind, strace).
>
> As HVM ops have no specific interface version, the main Xen interface version
> needs to be bumped to compensate.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Tim Deegan <tim@xen.org>
> CC: Ian Campbell <Ian.Campbell@citrix.com>
> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> ---
> This is a bugfix with regards to API versioning. There is no risk whatsoever
> from taking it, but there is an outstanding API breakage which it fixes.
> ---
> xen/include/public/xen-compat.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/include/public/xen-compat.h b/xen/include/public/xen-compat.h
> index 3eb80a0..c1d660d 100644
> --- a/xen/include/public/xen-compat.h
> +++ b/xen/include/public/xen-compat.h
> @@ -27,7 +27,7 @@
> #ifndef __XEN_PUBLIC_XEN_COMPAT_H__
> #define __XEN_PUBLIC_XEN_COMPAT_H__
>
> -#define __XEN_LATEST_INTERFACE_VERSION__ 0x00040400
> +#define __XEN_LATEST_INTERFACE_VERSION__ 0x00040500
>
> #if defined(__XEN__) || defined(__XEN_TOOLS__)
> /* Xen is built with matching headers and implements the latest interface. */
next prev parent reply other threads:[~2014-11-04 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 11:44 [PATCH for-4.5] xen: Bump several interface versions in preparation for Xen-4.5 Andrew Cooper
2014-11-04 11:46 ` Andrew Cooper [this message]
2014-11-04 11:50 ` [PATCH v2 for-4.5] xen: Bump Xen interface " Andrew Cooper
2014-11-04 12:00 ` Jan Beulich
2014-11-04 12:08 ` Ian Campbell
2014-11-04 12:24 ` Jan Beulich
2014-11-04 12:07 ` 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=5458BCA9.3000304@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.