Re: [Xen-devel] [PATCH v2 2/2] xen: implement VCPUOP_register_runstate_phys_memory_area

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 15.05.19 at 10:44, <andrii.anisov@xxxxxxxxx> wrote:
> On 14.05.19 16:49, Jan Beulich wrote:
>> If this was a concern only for newly written code, this would be fine.
>> But you need to make sure all existing code also continues to work
>> with whatever new interface you implement.
> 
> And that is one more reason why I tend to introduce the new interface in 
> parallel to be fully independent from the old one.
> But not do a mixed implementation as you and Julien suggest.

What behavior guests see and how it is implemented in the hypervisor
are two largely independent things. That is, we could choose to forbid
mixing of registration methods while still having some level of code
sharing between how both hypercall variants get actually processed.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel