Skip to content

Notify page fault call chain

Anil S Keshavamurthy lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 patches 2 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6Notify page fault call chain for i386arch/i386/kernel/traps.c arch/i386/mm/fault.c include/asm-i386/kdebug.h+29 -20 replies
2/6Notify page fault call chain for x86_64arch/x86_64/kernel/traps.c arch/x86_64/mm/fault.c include/asm-x86_64/kdebug.h+30 -22 replies
3/6Notify page fault call chain for ia64arch/ia64/kernel/traps.c arch/ia64/mm/fault.c include/asm-ia64/kdebug.h+28 -10 replies
4/6Notify page fault call chain for powerpcarch/powerpc/kernel/traps.c arch/powerpc/mm/fault.c include/asm-powerpc/kdebug.h+21 -10 replies
5/6Notify page fault call chain for sparc64arch/sparc64/kernel/traps.c arch/sparc64/mm/fault.c include/asm-sparc64/kdebug.h+28 -10 replies
6/6Kprobes registers for notify page faultkernel/kprobes.c+8 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [patch 0/6] Notify page fault call chain

Hi Andrew,

Currently in the do_page_fault() code path, we call notify_die(DIE_PAGE_FAULT, ...) to notify the page fault. The only interested components for this page fault notifications are Kprobes and/or kdb. Since notify_die() is highly overloaded, this page fault notification is currently being sent to other components registered with register_die_notification() which uses the same die_chain to loop for all the registered components.

In order to optimize the do_page_fault() code path, this critical page fault notification is now moved to different call chain and the test results showed great improvements.

Patches for i386, x86_64, ia64, powerpc and sparc64 follows this mail.

Please apply.

Thanks,
Anil Keshavamurthy

--