On 9/16/19 11:59 AM, Pawel Wieczorkiewicz wrote:
Having detailed hotpatch metadata helps to properly identify module's
origin and version. It also allows to keep track of the history of
hotpatch loads in the system (at least within dmesg buffer size
limits).
The hotpatch metadata are embedded in a form of .modinfo section.
Each such section contains data of the following format:
key=value\0key=value\0...key=value\0
The .modinfo section may be generated and appended to the resulting
hotpatch ELF file optionally as an extra step of a higher level
hotpatch build system.
The metadata section pointer and the section length is stored in the
hotpatch payload structure and is used to display the content upon
hotpatch apply operation.
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: Leonard Foerster <foers...@amazon.de>
Reviewed-by: Martin Pohlack <mpohl...@amazon.de>
Reviewed-by: Norbert Manthey <nmant...@amazon.de>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.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
