From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH] PoD: Handle operations properly when domain is dying Date: Thu, 12 Nov 2009 10:56:35 +0000 Message-ID: <4AFBE9E3.50306@eu.citrix.com> References: <3fc04a2c-ed3a-4bdf-a02b-313a2a70f068@default> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3fc04a2c-ed3a-4bdf-a02b-313a2a70f068@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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. -George