Lines Matching refs:which
31 The end of the document has a section titled `Not Yet Done` which
48 is responsible for identifying which mechanism to employ and how many locations
64 * One wants to query which modules have been loaded at runtime.
73 ISA is variable size which places limits on how much space we have available
108 bytes of code which alters all the offsets inside the function. To alter
113 which calls arch_do_domctl:
124 - which is not called directly by hypervisor but on behalf of the guests via
137 place where it is used is in `hvm_hypercall64_table` which would need
143 * changing the virtual address in all the functions which called the old
150 However it has drawbacks - the safety checks which have to make sure
167 for certain HYPERVISOR_xen_version sub-ops*) which mem-sets an structure
182 place where it is used is in `hvm_hypercall64_table` which would need
203 which would lessen the amount of patching to just one location.
206 new replacement function which required:
288 * `.livepatch.funcs` - which is an array of livepatch_func structures.
289 * `.livepatch.depends` - which is an ELF Note that describes what the payload
296 which describe the functions to be patched:
334 the new function (which will replace the one at `old_addr`) in bytes.
421 which follows the format of an ELF Note. The contents of this
457 one uint32_t to determine the sub-operations and one padding field which
475 which contains:
506 * A `struct xen_livepatch_name` called `name` which has the unique name.
533 * A `struct xen_livepatch_name` called `name` which has the unique name.
544 LIVEPATCH_ACTION_* operation. The normal values can be zero or -XEN_EAGAIN which
560 We apply an action - LIVEPATCH_ACTION_REVERT - to revert it (which won't work
598 recommended that on first invocation zero be used so that `nr` (which the
601 * `nr` the max number of entries to populate. Can be zero which will result
634 The `struct xen_livepatch_status` structure contains an status of payload which includes:
641 LIVEPATCH_ACTION_* operation. The normal values can be zero or -XEN_EAGAIN which
799 (specifically *stac* and *clac* operations) which is enabled on Broadwell
807 checks failing. Safety checks such as not patching code which
808 is on the stack - which can lead to corruption.
819 which ends up calling on_selected_cpus on remote CPUs.
830 To randezvous all the CPUs an barrier with an maximum timeout (which
851 This is implemented in a seperate tool which lives in a seperate
875 has a habit of coalescing strings that are the same - which means if we in-place
892 * all locations which use this string will have to be updated to use the
903 However, functions which are being patched can bring in changes to strings
943 The second option which requires an build-id of the hypervisor
966 * Further safety checks (blacklist of which functions cannot be patched, check
1125 this means 5 bytes are required which means that `old_size` **MUST** be