[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen memory management

  • To: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
  • From: David Xu <davidxu06@xxxxxxxxx>
  • Date: Thu, 23 Jun 2011 19:50:36 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 23 Jun 2011 16:51:18 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IIMtti32ksy83Kobns67NPB9ofeLEntTP84IXdvLRirUfIwE75f55TEjYtctbAeKN5 uMqJGX5ULx3vsN6i28fQnFf019vtxvSS30VzKxXbWWfWhOfQMOycwXjvym+zvOxZ1giF httfuHdJNIOqixBFPyrlkZr6nwTSr82MCJasg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.


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.

Xen-devel mailing list

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.