Lines Matching refs:at
64 * One wants to query which modules have been loaded at runtime.
81 A third mechanism is to add a jump to the new function at the
155 Having the patching done at predetermined instances where the stacks
219 since we are replacing at a higher level (a full function as opposed
222 Having the patching done at predetermined instances where the stacks
286 The payload contains at least three sections:
317 * `old_addr` is the address of the function to be patched and is filled in at
326 * If the value is zero, then we NOPing out at the `old_addr` location
334 the new function (which will replace the one at `old_addr`) in bytes.
347 structure and the core code inserts a trampoline at `old_addr` to `new_addr`.
451 The sub-operations will spell out how preemption is to be handled (if at all).
501 will be returned. The payload is not applied at this time - that is
511 payload. It can be embedded into the ELF payload at creation time
619 fail). The `status`, `name`, and `len`' are updated at their designed index
814 code and result in NMI. As such having the patching be done at the tail
827 This is a good spot because all Xen stacks are effectively empty at
854 Currently it resides at git://xenbits.xen.org/livepatch-build-tools.git
982 BUG() (or WARN()) macro and at that point embeds the source line number
1028 differ at exactly the location where a line-number is embedded.
1044 in memory. The signature is to be appended at the end of the ELF payload
1119 However if we need - we can always add two trampolines. One at the 2GB
1126 at least five bytes if patching in trampoline.
1152 This means that that `old_size` **MUST** be at least four bytes if patching