In article <1118281429.532953.2723.nullmailer@yamt.dyndns.org>,
YAMAMOTO Takashi  <yamt@mwd.biglobe.ne.jp> wrote:
> 
> besides that, xen_shm assumes an arbitrary request can be mapped into
> a single contiguous virtual address range.  it's wrong.

Also, it assumes that it will be mapping pages for only one xbd request
at a time; see XENSHM_MAX_PAGES_PER_REQUEST.  That will need some
adjusting if I want to piece together a whole MAXPHYS... and, while I'm
in this file, I wonder: is xen_shm's big piece of VM actually big enough
to handle use by both disk and net devices?

Oh, and: it's nice that the value of xen_shm_size is patchable, but
won't the size of _xen_shm_vaddr2ma[] be a little harder to manipulate
post-linking?

-- 
(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)))))