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] Review needed for "commonisation"ofcommon/grant_table.c

To: "Dong, Eddie" <eddie.dong@xxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <cwc22@xxxxxxxxx>
Subject: RE: [Xen-devel] Review needed for "commonisation"ofcommon/grant_table.c
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Tue, 14 Jun 2005 07:36:44 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 14 Jun 2005 14:35:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVuBlLakJ6ZKpDrS66Z9eBsen+ZAQAACwkgAAwg/8AAeuKgsAAA48NAAA2rMcAAC+ELEAAYbgIw
Thread-topic: [Xen-devel] Review needed for "commonisation"ofcommon/grant_table.c
> > I understand (I think) how it works on x86.  But the memory
> > model is somewhat different on ia64.  Domain 0 has access
> > to all of machine memory and can create a duplicate mapping
> > for any page of any unprivileged guest.  This is not controlled
> > by Xen (in the current implementation).
> Doesn't XEN/domain0 use ballon driver to give memory to HV and 
> let HV memory system allocate for other domains? Or are you proposing
> a new XEN memory mechanism (can you share with us for the details 
> so that we can be in same page if this is the case)? 
> But anyway I don't think IA64 has such kind of specials.

Throughout the development of Xen 3.0, more and more functionality
is moving out of the hypervisor and into domain0.  Management
of physical memory (outside of that memory which is required
for Xen itself) is a reasonable next step.  Because of architectural
constraints, this is harder for x86 but that's no reason to
constrain ia64, where machine memory is completely accessible
to domain0 and completely hidden from other domains.


Xen-devel mailing list

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