> On 21. Aug 2019, at 20:12, Konrad Rzeszutek Wilk
> wrote:
>
> On 8/14/19 4:39 AM, Pawel Wieczorkiewicz wrote:
>> #ifdef __XEN__
>> +typedef enum livepatch_func_state {
>> +LIVEPATCH_FUNC_NOT_APPLIED = 0,
>> +LIVEPATCH_FUNC_APPLIED = 1
>> +} livepatch_func_state_t;
>> +
>> struct
On 8/14/19 4:39 AM, Pawel Wieczorkiewicz wrote:
#ifdef __XEN__
+typedef enum livepatch_func_state {
+LIVEPATCH_FUNC_NOT_APPLIED = 0,
+LIVEPATCH_FUNC_APPLIED = 1
+} livepatch_func_state_t;
+
struct livepatch_func {
const char *name; /* Name of function to be patched. */
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
