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 <wipa...@amazon.de> > Reviewed-by: Andra-Irina Paraschiv <andra...@amazon.com> > Reviewed-by: Bjoern Doebel <doe...@amazon.de> > Reviewed-by: Martin Pohlack <mpohl...@amazon.de> > Signed-off-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com> > Acked-by: Julien Grall <julien.gr...@arm.com> Reviewed-by: Ross Lagerwall <ross.lagerw...@citrix.com>
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
