Subject: Re: uvm_page_physload
To: None <>
From: Jed Davis <>
List: tech-kern
Date: 08/29/2006 20:12:21
Chuck Cranor <> writes:

> that's a bug in the !VM_PHYSSEG_NOADD case.  but all ports 
> define VM_PHYSSEG_NOADD because the "ADD" case was never completed.
> (see the XXXCDC comment in uvm_page.c --- you need to update uvmexp
> and somehow sync the pmap in order to do a uvm_page_physload() after
> the VM has been inited.)
> that (incomplete) code is there because I was thinking about
> the case where you have a memory board that you want to add
> to the VM at autoconfig time.  [must have been thinking about
> mvme147 at the time...]

Xen, as I understand it, provides hot-pluggable memory -- arbitrary
page-aligned parts of the pseudo-physical address space can be
populated or released, provided that the total amount of machine
memory used doesn't exceed the domain's current memory limit.

(let ((C call-with-current-continuation)) (apply (lambda (x y) (x y)) (map
((lambda (r) ((C C) (lambda (s) (r (lambda l (apply (s s) l))))))  (lambda
(f) (lambda (l) (if (null? l) C (lambda (k) (display (car l)) ((f (cdr l))
(C k)))))))    '((#\J #\d #\D #\v #\s) (#\e #\space #\a #\i #\newline)))))