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] Xen memory management

To: David Xu <davidxu06@xxxxxxxxx>
Subject: Re: [Xen-devel] Xen memory management
From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Date: Fri, 24 Jun 2011 01:16:50 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Jun 2011 17:17:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTikm5Q8DNHr1VTwO6zmZL_e_Xnea+g@xxxxxxxxxxxxxx>
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: <BANLkTinmK9UogogAk0kn6qzNS12BXmfbLQ@xxxxxxxxxxxxxx> <20110623092711.GU17634@xxxxxxxxxxxxxxxxxxxxxxx> <BANLkTi=WzAQ5dugc4Gwm1-5pStcGCt0SpQ@xxxxxxxxxxxxxx> <4E03BA38.6060003@xxxxxxxxxxx> <BANLkTikm5Q8DNHr1VTwO6zmZL_e_Xnea+g@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv: Gecko/20110414 Thunderbird/3.1.10

On 24/06/2011 00:50, David Xu wrote:

2011/6/23 Jonathan Tripathy <jonnyt@xxxxxxxxxxx>

On 23/06/2011 23:08, David Xu wrote:
Thanks. My concern is that if several VMs are mapped to same memory, one VM may get something from the memory which has ever been used by another VM. This may cause some secure problems. 

Someone correct me if I'm wrong, but I'm pretty sure that a DomU kernel (If the flag is set correctly during compile time) will scrub (i.e. "zero") RAM first before releasing it to the Xen Hypervisor. Then hypervisor will then subsequently assign that bit of RAM to another domain.

Sounds good. Does Xen VMM can control the mapping between a part of memory and cache line? That is to say I wander whether Xen can guarantee different VMs will use different cache line. Thanks.


Please don't top post :)

I'm not a Xen dev, so it would be great if a dev could let me know if I'm talking rubbish or not. However from my very limited knowledge of how CPU caches work (which comes from basic single CPU, non VMM related system), common sense would tell me that the cache line would be different for each DomU, as a CPUs cache is inherently linked to main memory (RAM). I believe that the process used to access data from memory is abstracted by the CPU, so assuming that Xen prevents access to RAM from another DomU, I guess it would make sense to say that any data that is cached in the CPU is protected.

Then again, I could be completly wrong......

Xen-devel mailing list