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

Re: [Xen-devel] HVM dynamic physical memory

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] HVM dynamic physical memory
From: "David Pilger" <pilger.david@xxxxxxxxx>
Date: Sun, 31 Dec 2006 15:26:32 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 31 Dec 2006 05:26:17 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jmMUYEhmd5h1mIFFhkvUtpvBiZs+v+3tLYvF09lUkb8F05wwG8tO3JcZQi8HGylOYo+vuPOxdOMPq2Uy0A0u5mbDNZ9SPJBS0s5Gx28ujg8+qeJP4cPsCljJIIYffRnLh/rQHbsqOFK7J0DHtZeyqarBod+6fyP09EhZTe0WllM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1BD66D3.68DF%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <280848580612310503i2283c5f7ub13f6697c4387c42@xxxxxxxxxxxxxx> <C1BD66D3.68DF%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 12/31/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
On 31/12/06 1:03 pm, "David Pilger" <pilger.david@xxxxxxxxx> wrote:

> On 12/31/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
>>
>> All that's missing is the balloon driver itself (but the PV Linux one could
>> be used as a basis), support for using the memory-reservation hypercall from
>> HVM context, and a way to blow away qemu's memory-mapping cache when memory
>> is given back to Xen from the HVM guest.
>>
>
> If you plan to not modify the HVM, Is there a way to make portions of
> physical memory unusable for a HVM windows from the hypervisor in a
> dynamic way?

In a way that is detectable by the guest OS in a way that causes it to react
in a reasonable way? Unlikely, since there is no equivalent of this on a
native x86 platform.


Pretty conclusive :)
Thanks!

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

<Prev in Thread] Current Thread [Next in Thread>