[XenAccess-devel] Page mapping protections

[<hi...@cc...>]

Hi Bryan,

Although the individual mapping functions accept page protection arguments,
none of the public functions allows for anything but PROT_READ access.
There are reasons, however, for allowing PROT_WRITE (or even  
PROT_EXEC) access.
Perhaps the most general reason is lock grabbing.  For example,  
doesn't walking
the process list require a lock?  I think it's incorrect to iterate over the
tasks list without holding a lock (although the probability of generating an
incorrect list is apparently very low).

I would like some of the public functions, like xa_access_virtual* to  
include arguments for page protections.

What is your opinion?

-Jim