Xen devel - Jan 2010 - [PATCH, RFC 0/4] tools interface changes for supporting MFNs with 32 or more significant bits

In order to support now possible MFNs with 32 (or more) significant bits,
two changes are required to the interfaces the Dom0 tools use: The
individual page error indication must no longer be or-ed into the passed
in MFN (because the bits used by the error indicator may collide with
non-zero bits in the MFN), and a replacement for
XEN_DOMCTL_getpageframeinfo2 is needed where full-width MFNs can
be passed in and the result is being returned in a non-ambiguous way.

1) linux: add new (replacement) mmap-batch ioctl
2) libxc: use new (replacement) mmap-batch ioctl
3) qemu: use new (replacement) mmap-batch ioctl
4) add and use XEN_DOMCTL_getpageframeinfo3

The fact that pfn and its type get encoded as a 32-bit quantity when
writing the save image means that save/restore in its current shape
can''t support guests with a physical address space covering more than
1Tb. It''s not clear to me whether this can be fixed in a compatible
way.

In case the (lightly tested only so far) changes are acceptable as-is:
Signed-off-by: Jan Beulich <jbeulich@novell.com>

Jan






_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel