On Tuesday 02 May 2006 05:45, Nick Piggin wrote:
blaisorblade@xxxxxxxx wrote:
The first idea is to use this for UML - it must create a lot of single
page mappings, and managing them through separate VMAs is slow.
I think I would rather this all just folded under VM_NONLINEAR rather than
having this extra MANYPROTS thing, no? (you're already doing that in one
direction).
That step is _temporary_ if the extra usages are accepted.
Also, I reported (changelog of patch 03/14) a definite API bug you get if you don't distinguish VM_MANYPROTS from VM_NONLINEAR. I'm pasting it here because that changelog is rather long:
"In fact, without this flag, we'd have indeed a regression with
remap_file_pages VS mprotect, on uniform nonlinear VMAs.
mprotect alters the VMA prots and walks each present PTE, ignoring installed
ones, even when pte_file() is on; their saved prots will be restored on faults,
ignoring VMA ones and losing the mprotect() on them. So, in do_file_page(), we
must restore anyway VMA prots when the VMA is uniform, as we used to do before
this trail of patches."
Ulrich wanted to have code+data(+guard on 64-bit) into the same VMA, but I left the code+data VMA joining away, to think more with it, since currently it's too slow on swapout.
The other part is avoiding guard VMAs for thread stacks, and that could be accomplished too by your proposal. Iff this work is held out, however.