[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: /dev/mem and /dev/kmem
On 21/3/07 12:35, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote: > So how about applications which simply use /dev/mem to map > normal domain memory? Seems this breaks compatibility > in user level though desired for above Xserver case... Or such > case is rare? This case seems not to occur in practise (no complaints so far and our /dev/mem has had this limitation since day one). This is perhaps not surprising: really not much good can come out of direct grokking of kernel-maintained memory without the kernel's knowledge. > BTW, I didn't find code to protect Xen to be mapped in this path, > like in get_page_from_l1e(). Could you help pointing out? Not sure how you mean. Only pages that explicitly are owned by a domain and have a non-zero refcount can have get_page() succeed on them. So random Xen-owned pages are safe. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |