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

[Andrii Anisov <andrii.anisov@xxxxxxxxx>]

Hello Jan,

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.

> Just because a kernel
> uses your new physical address based mechanism doesn't mean the
> boot loader knows to unregister what it has registered.
As Julien already said, the current interface has an implicit mechanism to 
unregister runstate area.
Also if the bootloader misses unregistering runstate area with the current 
interface, we already have the broken system.
So it is really up to the guest system to take care about its possible 
transitions.

--
Sincerely,
Andrii Anisov.

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