[patch 07/10] Page fault handler should not depend on CONFIG_KPROBES

[Anton Blanchard]

> NACK until the performace implication a fixed.  Martin measured this
> costs 300 cycles on s390 even without any notifier activce, and while
> ppc might be slightly bad that's still too much to add to the pagefault
> handler unconditionally.  Please add a light weight method to check
> whether there is any activce user of the notifications.  Also please
> move the code into kernel/ at the same time instead of having the exact
> same thing duplicated all over, as in my notify_die patches.

Im struggling to understand how they could take 300 cycles to execute
this code sequence. We have seen similar questions on the ia64 side,
they both must have some pretty fundamental branch prediction issues.

I measured this in sim and the sequence takes under 20 cycles on a
power5 class machine, and thats a pessimistic estimate.

Anton