Notify page fault call chain
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | Notify page fault call chain for i386arch/ arch/ include/ | +29 | 0 replies | |
| 2/6 | Notify page fault call chain for x86_64arch/ arch/ include/ | +30 | 2 replies | |
| 3/6 | Notify page fault call chain for ia64arch/ arch/ include/ | +28 | 0 replies | |
| 4/6 | Notify page fault call chain for powerpcarch/ arch/ include/ | +21 | 0 replies | |
| 5/6 | Notify page fault call chain for sparc64arch/ arch/ include/ | +28 | 0 replies | |
| 6/6 | Kprobes registers for notify page faultkernel/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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
--