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] Re: [Xen-changelog] New memory_op subops which return th

To: Chris Wright <chrisw@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] New memory_op subops which return the apparent or actual physical address map.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 26 May 2006 10:25:27 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian.Campbell@xxxxxxxxxxxxx
Delivery-date: Fri, 26 May 2006 02:30:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060526092308.GB25508@xxxxxxxxxxxxxxxxx>
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: <E1FiFuu-0005WW-LE@xxxxxxxxxxxxxxxxxxxxx> <20060526092308.GB25508@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 26 May 2006, at 10:23, Chris Wright wrote:

+    case XENMEM_memory_map:
+    {
+        return -ENOSYS;
+    }

Is this meant to be a place holder?  Did you plan to replace the
hardcoded single entry map later?

It will be properly defined for mini-xen, where it will return the real physical memory map. It could also be properly defined for auto-translate guests (where Xen manages the pseudo-physical space and therefore it is reasonable for Xen to provide the pseuophys e820 map). It could also be properly defined for all guests if the guest loader could poke down e820 maps.

 -- Keir

Xen-devel mailing list

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