On Mon, 2007-07-23 at 13:27 +0300, Avi Kivity wrote: > Having an address_space (like your patch does) is remarkably simple, and > requires few hooks from the current vm. However using existing vmas > mapped by the user has many advantages: > > - compatible with s390 requirements > - allows the user to use hugetlbfs pages, which have a performance > advantage using ept/npt (but which are unswappable) > - allows the user to map a file (which can be regarded as way to specify > the swap device) > - better ingration with the rest of the vm
You don't need to expose the vmas. You just have userspace point out the start+len of each region of memory it wants the guest to be able to access, and the address it wants it to appear in the guest. This is a slight superset of what lguest does in two ways: 1) my guest address == user address, but I'm looking at adding an offset so I don't have to link the launcher binary specially. 2) I have only one contiguous region of guest-physical memory, since I can place device memory immediately above "normal" mem. But the result is pretty sweet, and doesn't require any new symbols to be exported. Cheers, Rusty. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
