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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] PoD: Handle operations properly when domain is d

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] PoD: Handle operations properly when domain is dying
From: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
Date: Thu, 12 Nov 2009 10:56:35 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 12 Nov 2009 03:01:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3fc04a2c-ed3a-4bdf-a02b-313a2a70f068@default>
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>
References: <3fc04a2c-ed3a-4bdf-a02b-313a2a70f068@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090817)
Dan Magenheimer wrote:
I understand that from your (developer's) point of view
but 99% or more of your customers won't know what a p2m
table is or what populating it means and will assume
(as I did earlier), since this is a memory-related
feature, that "populate" refers to utilizing RAM.
Since almost all the code referring to PoD is in a place that only a devloper should look (in the hypervisor, and a little bit in the hvm domain builder), I think the naming (at least internally) is appropriate. One could imagine "shadow memory" being mis-interpreted in a similar fashion. :-)

PoD is only one piece of the puzzle required to allow booting pre-ballooned. If you feel like we need a name "marketing name" for the whole feature to put in annoucements and changelogs, feel free to suggest one. :-)

In XenServer, the whole thing will come under the umbrella of "Dynamic Memory Control".

I guess that makes sense in the Windows world where "distros"
can be counted on one or two hands.
My guess is that Linux as a whole will have much less variance than Windows. But we're not testing HVM Linux ATM.


Xen-devel mailing list