From: Jim Fehlig <jfehlig@suse.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: LibVirt Development List <libvir-list@redhat.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] libxl: use LIBXL_API_VERSION 0x040200
Date: Thu, 14 Apr 2016 16:32:43 -0600 [thread overview]
Message-ID: <57101A8B.3030306__20616.7476172142$1460673398$gmane$org@suse.com> (raw)
In-Reply-To: <CAFLBxZbNpBvmXZqSx6ib1ryAOQXscYLOM-gQqomhvNCKkLWOjg@mail.gmail.com>
George Dunlap wrote:
> On Thu, Apr 14, 2016 at 12:37 AM, Jim Fehlig <jfehlig@suse.com> wrote:
>> To ensure the libvirt libxl driver will build with future versions
>> of Xen where the libxl API may change in incompatible ways,
>> explicitly use LIBXL_API_VERSION 0x040200. The libxl driver
>> does use new libxl APIs that have been added since Xen 4.2, but
>> currently it does not make use of any changes made to existing
>> APIs such as libxl_domain_create_restore or libxl_set_vcpuaffinity.
>> The version can be bumped if/when the libxl driver consumes the
>> changed APIs.
>>
>> Further details can be found in the following discussion thread
>>
>> https://www.redhat.com/archives/libvir-list/2016-April/msg00178.html
>> Signed-off-by: Jim Fehlig <jfehlig@suse.com>
>> ---
>> src/Makefile.am | 1 +
>> src/libxl/libxl_conf.h | 12 ------------
>> src/libxl/libxl_domain.c | 15 ---------------
>> 3 files changed, 1 insertion(+), 27 deletions(-)
>>
>> diff --git a/src/Makefile.am b/src/Makefile.am
>> index 08ff301..259a474 100644
>> --- a/src/Makefile.am
>> +++ b/src/Makefile.am
>> @@ -1311,6 +1311,7 @@ endif ! WITH_DRIVER_MODULES
>>
>> libvirt_driver_libxl_impl_la_CFLAGS = \
>> $(LIBXL_CFLAGS) \
>> + -DLIBXL_API_VERSION=0x040200 \
>> -I$(srcdir)/access \
>> -I$(srcdir)/conf \
>> -I$(srcdir)/secret \
>> diff --git a/src/libxl/libxl_conf.h b/src/libxl/libxl_conf.h
>> index 3c0eafb..24e2911 100644
>> --- a/src/libxl/libxl_conf.h
>> +++ b/src/libxl/libxl_conf.h
>> @@ -69,18 +69,6 @@
>> # endif
>>
>>
>> -/* libxl interface for setting VCPU affinity changed in 4.5. In fact, a new
>> - * parameter has been added, representative of 'VCPU soft affinity'. If one
>> - * does not care about it (and that's libvirt case), passing NULL is the
>> - * right thing to do. To mark that change, LIBXL_HAVE_VCPUINFO_SOFT_AFFINITY
>> - * is defined. */
>> -# ifdef LIBXL_HAVE_VCPUINFO_SOFT_AFFINITY
>> -# define libxl_set_vcpuaffinity(ctx, domid, vcpuid, map) \
>> - libxl_set_vcpuaffinity((ctx), (domid), (vcpuid), (map), NULL)
>> -# define libxl_set_vcpuaffinity_all(ctx, domid, max_vcpus, map) \
>> - libxl_set_vcpuaffinity_all((ctx), (domid), (max_vcpus), (map), NULL)
>> -# endif
>
> Just checking with this -- the LIBXL_API_VERSION is meant for
> *forward* compatibility, but I think the LIBXL_HAVE_* macros are for
> *backwards* compatibility, isn't that right? If you compile this
> against an older version of Xen without LIBXL_HAVE_VCPU_SOFT_AFFINITY
> (say, 4.4), will it break with this patch?
I've tested the patch (well, actually a variant that moves
'-DLIBXL_API_VERSION=0x040200' to configure.ac as suggested by Martin) by
building against 4.2, 4.3, 4.4, and 4.7/master. I think Dario already did a good
job explaining the removal of the above hunk.
Regards,
Jim
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-14 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 23:37 [PATCH] libxl: use LIBXL_API_VERSION 0x040200 Jim Fehlig
2016-04-14 7:41 ` Dario Faggioli
2016-04-14 8:11 ` [libvirt] " Martin Kletzander
2016-04-14 22:37 ` Jim Fehlig
2016-04-14 8:33 ` George Dunlap
[not found] ` <CAFLBxZbNpBvmXZqSx6ib1ryAOQXscYLOM-gQqomhvNCKkLWOjg@mail.gmail.com>
2016-04-14 12:55 ` Dario Faggioli
2016-04-14 22:32 ` Jim Fehlig [this message]
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='57101A8B.3030306__20616.7476172142$1460673398$gmane$org@suse.com' \
--to=jfehlig@suse.com \
--cc=george.dunlap@citrix.com \
--cc=libvir-list@redhat.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).