Le 21/09/2016 à 07:58, matthew green a écrit :
"Maxime Villard" writes:
Module Name: src
Committed By: maxv
Date: Sat Sep 17 12:00:35 UTC 2016
Modified Files:
src/sys/kern: kern_proc.c
Log Message:
Use VM_MAXUSER_ADDRESS for proc0, not VM_MAX_ADDRESS. It normally does not
change anything, since kernel processes use the shared kernel map instead
of the one they are given here. For consistency though, it is better to
make sure UVM will not be tempted to access machine-dependent reserved
areas (e.g., the PTE space on x86).
can you explain why this is right on platforms without shared
user/kernel address spaces? this change seems specific to
platforms that are forced or choose to merge them.
On these architectures VM_MAX_ADDRESS = VM_MAXUSER_ADDRESS, so who cares? Yes,
this change is specific to platforms with a shared va space; and in fact, it
might even be specific to x86 (I haven't given a careful look at the others).
