On 09/30/2015 06:34 PM, Jan Beulich wrote: >>>> On 30.09.15 at 17:28, <rcojoc...@bitdefender.com> wrote: >> On 09/30/2015 06:25 PM, Julien Grall wrote: >>> Hi, >>> >>> On 30/09/15 16:16, Razvan Cojocaru wrote: >>>> VM_EVENT_FLAG_SET_REGISTERS and xc_monitor_emulate_each_rep() are >>>> not available in Xen 4.6, hence the bump. >>> >>> Shouldn't you bump XEN_DOMCTL_INTERFACE_VERSION and >>> VM_EVENT_INTERFACE_VERSION instead? >>> >>> The former for xc_monitor_emulate_each_read as it's a DOMCTL and the >>> latter for VM_EVENT_FLAG_SET_REGISTERS? >> >> Yes, judging also by Jan's previous comment that would appear to be the >> preferred way to go. > > I can't talk about VM_EVENT_INTERFACE_VERSION, but I also > don't see any reason to bump XEN_DOMCTL_INTERFACE_VERSION > with the given change. Again - it's just an addition to the interface, > not an incompatible change.
The same is true for VM_EVENT_FLAG_SET_REGISTERS I'm afraid. Nothing at all changes for existing vm_event users. In that case, I'll just leave them all alone. But the question still remains, if these markers are unreliable in my case, could you please suggest another which I can check in my scenario? __XEN_LATEST_INTERFACE_VERSION__ has been fine so far, but I now see that this has only been a coincidence. Thanks, Razvan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
