Re: [Xen-devel] [PATCH] xen: Bump __XEN_LATEST_INTERFACE_VERSION__ to 0x00040700

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 30.09.15 at 17:27, <rcojocaru@xxxxxxxxxxxxxxx> wrote:
> On 09/30/2015 06:23 PM, Jan Beulich wrote:
>>>>> On 30.09.15 at 17:16, <rcojocaru@xxxxxxxxxxxxxxx> wrote:
>>> VM_EVENT_FLAG_SET_REGISTERS and xc_monitor_emulate_each_rep() are
>>> not available in Xen 4.6, hence the bump.
>> 
>> I don't follow: These are additions, not changes that require
>> consumers to adapt their code.
> 
> I have code that checks for __XEN_LATEST_INTERFACE_VERSION__ and if it
> is 0x00040700 then it uses xc_monitor_emulate_each_rep(), otherwise it
> knows it can't - I thought that consumers that want to make use of the
> latest API should be able to tell that they're allowed to do so.
> 
> But if the Xen convention is to only bump it when the interface is no
> longer backward compatible then I've misunderstood (in which case, sorry
> for the noise, and also, is there another way to tell which Xen version
> I'm compiling against?).

Just check for the relevant #define to be there.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel