WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH, RFC 0/4] tools interface changes for supporting MFNs

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH, RFC 0/4] tools interface changes for supporting MFNs with 32 or more significant bits
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 11 Jan 2010 14:49:16 +0000
Delivery-date: Mon, 11 Jan 2010 06:50:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxx>

Jan

Attachment: xen-qemu-privcmd-mmap-new.patch
Description: Text document

Attachment: xen-domctl-getpageframeinfo3.patch
Description: Text document

Attachment: xen-libxc-privcmd-mmap-new.patch
Description: Text document

Attachment: xenlinux-privcmd-mmap-batch-new.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH, RFC 0/4] tools interface changes for supporting MFNs with 32 or more significant bits, Jan Beulich <=