search for: text_pok

...t;x86/paravirt: Add primitives to stage pv-ops" > > Patch 20 enables switching of pv_lock_ops: > "x86/paravirt: Enable pv-spinlocks in runtime_patch()" > > 2. Non-emulated text poking (patches 11-19) > > Patches 11-13 are mostly refactoring to split __text_poke() into map, > unmap and poke/memcpy phases with the poke portion being re-entrant > "x86/alternatives: Remove return value of text_poke*()" > "x86/alternatives: Use __get_unlocked_pte() in text_poke()" > "x86/alternatives: Split __text_poke()" &...

...Dc0490000) Stack: 00000001 c04509a4 c0107ca2 c010fc1e c010fc23 c010e474 e84b719c 00000= 001 = 00000001 c010fc24 c0450a40 c0107d9f c04b8f58 c04bf2f0 c04abee0 00000= 000 = c0107df2 00000006 00010202 c0491ff0 c04975fa c04ac2a0 c0492aba 00000= 080 = Call Trace: [<c0107ca2>] text_poke+0x22/0xd0 [<c010fc1e>] lookup_address+0x1e/0x70 [<c010fc23>] lookup_address+0x23/0x70 [<c010e474>] paravirt_patch_call+0x44/0x60 [<c010fc24>] lookup_address+0x24/0x70 [<c0107d9f>] nop_out+0x4f/0x60 [<c0107df2>] apply_paravirt+0x42/0x50 [<c04975f...

...Dc0490000) Stack: 00000001 c04509a4 c0107ca2 c010fc1e c010fc23 c010e474 e84b719c 00000= 001 = 00000001 c010fc24 c0450a40 c0107d9f c04b8f58 c04bf2f0 c04abee0 00000= 000 = c0107df2 00000006 00010202 c0491ff0 c04975fa c04ac2a0 c0492aba 00000= 080 = Call Trace: [<c0107ca2>] text_poke+0x22/0xd0 [<c010fc1e>] lookup_address+0x1e/0x70 [<c010fc23>] lookup_address+0x23/0x70 [<c010e474>] paravirt_patch_call+0x44/0x60 [<c010fc24>] lookup_address+0x24/0x70 [<c0107d9f>] nop_out+0x4f/0x60 [<c0107df2>] apply_paravirt+0x42/0x50 [<c04975f...

...instructions as usual at init. This is then > used for switching back and forth between native and paravirt mode. > ([1] lists some representative numbers of the increased memory > footprint.) > > Mechanism: the patching itself is done using stop_machine(). That is > not ideal -- text_poke_stop_machine() was replaced with INT3+emulation > via text_poke_bp(), but I'm using this to address two issues: > 1) emulation in text_poke() can only easily handle a small set > of instructions and this is problematic for inlined pv-ops (and see > a possible alternatives use-ca...

...instructions as usual at init. This is then > used for switching back and forth between native and paravirt mode. > ([1] lists some representative numbers of the increased memory > footprint.) > > Mechanism: the patching itself is done using stop_machine(). That is > not ideal -- text_poke_stop_machine() was replaced with INT3+emulation > via text_poke_bp(), but I'm using this to address two issues: > 1) emulation in text_poke() can only easily handle a small set > of instructions and this is problematic for inlined pv-ops (and see > a possible alternatives use-ca...

On 08.04.20 14:08, Peter Zijlstra wrote: > On Tue, Apr 07, 2020 at 10:02:57PM -0700, Ankur Arora wrote: >> Mechanism: the patching itself is done using stop_machine(). That is >> not ideal -- text_poke_stop_machine() was replaced with INT3+emulation >> via text_poke_bp(), but I'm using this to address two issues: >> 1) emulation in text_poke() can only easily handle a small set >> of instructions and this is problematic for inlined pv-ops (and see >> a possible...

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined