Re: [patch] x86: optimise page fault entry

From: Ingo Molnar
Date: Tue Jan 20 2009 - 05:10:23 EST

* Nick Piggin <npiggin@xxxxxxx> wrote:

> Hi,
> Sorry for the delay with this. The kernel ended up unbootable for me
> when I last dusted off the patch, so I couldn't test it and then
> promptly got sidetracked with other things.
> Anyway, this one is tested with a boot, some basic segfault sigbus etc
> tests, and passes various of the mmap and mprotect etc. ltp tests.
> Ingo, would you merge this into the x86 tree, please? (unless Linus has
> any objections to this version)

-tip testing found a 32-bit boot regression, caused by this patch. The
bootup hangs early, during the WP write-test check:

[ 0.004000] .data : 0xc0691f05 - 0xc09c746c (3285 kB)
[ 0.004000] .text : 0xc0100000 - 0xc0691f05 (5703 kB)
[ 0.004000] Checking if this processor honours the WP bit even in supervisor mode...

i've excluded x86/mm from tip/master for now, you can find the broken tree
in the tip/ [v2.6.29-rc2-1069-g583f1b9] branch that i
just pushed out:


Also, a patch structure sidenote, the diffstat is rather large:

arch/x86/mm/fault.c | 436 ++++++++++++++++++++++++++++++---------------------
1 files changed, 255 insertions(+), 181 deletions(-)

this shuffles 300 lines of highly critical x86 code around - which makes
me nervous. A finegrained, bisectable series would be far more debuggable.
Had we such a lineup i could have auto-bisected it for you already - while
now you have to see which bit of the ~500 lines of code flux broke the
32-bit WP test.

This hang might be easy to find and fix (the WP detect logic is simple),
but other failure modes might be less debuggable and this codepath deals
with a lot of obscure details like CPU errata. So it would be really nice
to have a finegrained splitup of this patch.

Three separate testsystems triggered this hang so it should be readily


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at