RE: [Xen-devel] [patch] more correct pfn_valid()

To:	"Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Scott Parish" <srparish@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] [patch] more correct pfn_valid()
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Thu, 19 May 2005 07:51:17 +0100
Delivery-date:	Thu, 19 May 2005 06:50:52 +0000
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcVb9aZ7Rlj1GNpbTJqBIcUW7A2ChAAANsGgAAkVbyAACQmCUA==
Thread-topic:	[Xen-devel] [patch] more correct pfn_valid()

 

> Agree with the approach for virtual frame_table to support 
> big hole, just like virtual memmap in Linux working currently 
> on large machine.
> However this one actually throws a brick about how to support 
> large hole of DomU.

Guests can have arbitrary sparse machine memory maps already on x86.

Ian

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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

[Xen-devel] VT spec on Web, Nakajima, Jun

Next by Date:

RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin

Previous by Thread:

RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin

Next by Thread:

RE: [Xen-devel] [patch] more correct pfn_valid(), Tian, Kevin

Indexes:

[Date] [Thread] [Top] [All Lists]

WARNING - OLD ARCHIVES

xen-devel

RE: [Xen-devel] [patch] more correct pfn_valid()