MM populate cleanup
authorBarret Rhoden <brho@cs.berkeley.edu>
Tue, 18 Feb 2014 00:29:03 +0000 (16:29 -0800)
committerBarret Rhoden <brho@cs.berkeley.edu>
Tue, 18 Feb 2014 03:49:30 +0000 (19:49 -0800)
commitb8a36b430b1ccf84afe70254ca072c8cb375a7cc
treeda2dc21a4d39f00714df7f3d2db7de7cdb22a3c3
parent1a5f41c68be99fb17798c82afa8a6830105c3845
MM populate cleanup

The main thing is the use of a history counter, which allows us to
detect changes in the VMRs, whether that change is just some prot
settings, or the existence of VMRs, etc.  While we can't reinspect the
vmr memory across an unlock-and-block, the history tells us it is safe
to keep following our previous instructions (keep mmaping a range of
pages).
kern/include/env.h
kern/src/mm.c
kern/src/process.c