This is exactly why 2.5.17 has the "tlb_remove_pte_entry()", and why it is
passed down the pte that we just cleared out - so that architectures can
hide details like this in the page tables (the other use is to hide things
like "iTBL vs dTLB" etc).
Sp why don't you just make "tlb_remove_pte_entry()" look at your bit, and
then if that bit is set you try to remove the entry from the hash chains
at that point?
You _have_ to do it this way, in fact, since reserved pages and other
"VM-invisible" pages aren't even passed down to "tlb_remove_page()"
(because they have no freeing logic, and they have no impact on RSS).
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/