Lines Matching refs:patch
5 A mechanism is required to binarily patch the running hypervisor with new
21 * splice - patch in the binary code with new opcodes
37 ## Multiple ways to patch
39 The mechanism needs to be flexible to patch the hypervisor in multiple ways
52 to patch. Combinations of modifying in-place code, adding trampoline, etc
74 The first mechanism to patch that comes in mind is in-place replacement.
92 and we would like to binary patch the hypervisor with it. The original code
120 Astute readers will wonder what we need to do if we were to patch `do_domctl`
176 An alternative solution would be to patch insert a trampoline in the
366 When applying the patch the hypervisor iterates over each `livepatch_func`
370 When reverting a patch, the hypervisor iterates over each `livepatch_func`
561 See "Live patch interdependencies" for more information.
650 xen_livepatch_name_t name; /* IN, name of the patch. */
851 xen_livepatch_name_t name; /* IN, name of the patch. */
917 3. *XEN_SYSCTL_LIVEPATCH_ACTION* with *LIVEPATCH_ACTION_APPLY* to apply the patch.
937 can leave the areas alone or patch them with an better suited opcodes.
944 ### When to patch
948 minimize the chance of the patch not being applied due to safety
955 every second. Using the `stop_machine` to patch can stall the time rendezvous
1008 As found almost every patch (XSA) to a non-trivial function requires
1016 also able to patch the strings as needed. This sounds simple - but the compiler
1020 This is also where pointers to functions live - and we may need to patch this
1028 * Inline patch.
1059 ### Live patch interdependencies
1061 Live patch patches interdependencies are tricky.
1064 * A single large patch that subsumes and replaces all previous ones.
1065 Over the life-time of patching the hypervisor this large patch
1076 The disadvantage of the first large patch is that it can grow over
1079 The hot-patch stack puts stricts requirements on the order of the patches
1109 * Be able to patch .rodata, .bss, and .data sections.
1130 Now we want to hotpatch f1 and the hotpatch source-code patch adds 2
1133 functions f1 (because we actually changed it with the applied patch) and
1154 that unnecessarily patch many functions.
1163 The decision between 1. and 2. can be made on a patch--by-patch
1170 We might either use this indirection table for runtime use and patch