On 9/28/19 4:13 PM, Pawel Wieczorkiewicz wrote: > Livepatch only tracks an entire payload applied/reverted state. But, > with an option to supply the apply_payload() and/or revert_payload() > functions as optional hooks, it becomes possible to intermix the > execution of the original apply_payload()/revert_payload() functions > with their dynamically supplied counterparts. > It is important then to track the current state of every function > being patched and prevent situations of unintentional double-apply > or unapplied revert. > > To support that, it is necessary to extend public interface of the > livepatch. The struct livepatch_func gets additional field holding > the applied/reverted state marker. > > To reflect the livepatch payload ABI change, bump the version flag > LIVEPATCH_PAYLOAD_VERSION up to 2. > > [And also update the top of the design document] > > Signed-off-by: Pawel Wieczorkiewicz <[email protected]> > Reviewed-by: Andra-Irina Paraschiv <[email protected]> > Reviewed-by: Bjoern Doebel <[email protected]> > Reviewed-by: Martin Pohlack <[email protected]> > Signed-off-by: Konrad Rzeszutek Wilk <[email protected]> > Acked-by: Julien Grall <[email protected]> Reviewed-by: Ross Lagerwall <[email protected]>
_______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
