+linux-arch FYI most preempt_enable_no_resched() calls outside of core scheduler code come from kprobes copy-and-paste, and can possibly be fixed in similar ways as this series. It's a bit of a footgun API that should be banished from outside kernel/sched/, at least without an explicit comment for each case that explains the need and how the missed resched is resolved or not applicable. Thanks, Nick On Fri Oct 21, 2022 at 3:28 AM AEST, Naveen N. Rao wrote: > This series attempts to address some of the concerns raised in > https://github.com/linuxppc/issues/issues/440 > > The last two patches are minor cleanups in related kprobes code. > > - Naveen > > > Naveen N. Rao (5): > powerpc/kprobes: Remove preempt disable around call to get_kprobe() in > arch_prepare_kprobe() > powerpc/kprobes: Have optimized_callback() use preempt_enable() > powerpc/kprobes: Use preempt_enable() rather than the no_resched > variant > powerpc/kprobes: Setup consistent pt_regs across kprobes, optprobes > and KPROBES_ON_FTRACE > powerpc/kprobes: Remove unnecessary headers from kprobes > > arch/powerpc/kernel/kprobes-ftrace.c | 4 ---- > arch/powerpc/kernel/kprobes.c | 16 ++++++---------- > arch/powerpc/kernel/optprobes.c | 2 +- > arch/powerpc/kernel/optprobes_head.S | 5 +---- > arch/powerpc/kernel/trace/ftrace_mprofile.S | 6 ++++++ > 5 files changed, 14 insertions(+), 19 deletions(-) > > > base-commit: 7dc2a00fdd44a4d0c3bac9fd10558b3933586a0c > -- > 2.38.0
