Message ID | 20191010151111.22125-2-ian.jackson@eu.citrix.com (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | libxl memkb & pt defaulting | expand |
On 10/10/19 9:11 AM, Ian Jackson wrote: > According to git log -G: > > 0x040700 was introduced in 304400459ef0 (aka 4.7.0-rc1~481) > "tools/libxl: rename remus device to checkpoint device" > > 0x040800 was introduced in 57f8b13c7240 (aka 4.8.0-rc1~437) > "libxl: memory size in kb requires 64 bit variable" > > It is surprising that no-one noticed this. I am now noticing it :-(. As Anthony noted in V1, libvirt uses LIBXL_API_VERSION and currently has it set to 0x040500. I'm attempting to bump libvirt's minimum supported Xen version to 4.9.0 and for that would use 0x040800, but it's not possible without this commit backported through 4.9 and picked up and released by all the downstreams. Any ideas on how to use the APIs changes through 0x040800, but avoid the ones introduced in 0x041300 would be much appreciated. Regards, Jim
diff --git a/tools/libxl/libxl.h b/tools/libxl/libxl.h index 2555e9cd3b..518fc9e47f 100644 --- a/tools/libxl/libxl.h +++ b/tools/libxl/libxl.h @@ -655,6 +655,7 @@ typedef struct libxl__ctx libxl_ctx; #ifdef LIBXL_API_VERSION #if LIBXL_API_VERSION != 0x040200 && LIBXL_API_VERSION != 0x040300 && \ LIBXL_API_VERSION != 0x040400 && LIBXL_API_VERSION != 0x040500 && \ + LIBXL_API_VERSION != 0x040700 && LIBXL_API_VERSION != 0x040800 && \ LIBXL_API_VERSION != 0x041300 #error Unknown LIBXL_API_VERSION #endif