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


[Xen-devel] Re: [Xen-changelog] Convert x86/64 Linux to use the new memo

To: Chris Wright <chrisw@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [Xen-changelog] Convert x86/64 Linux to use the new memory map hypercall.
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Fri, 26 May 2006 11:31:45 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 26 May 2006 03:32:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060526091715.GA25508@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: <E1FiFuv-0005X4-Mf@xxxxxxxxxxxxxxxxxxxxx> <20060526091715.GA25508@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2006-05-26 at 02:17 -0700, Chris Wright wrote:
> This breaks the native build.  I fixed it with the ugly hack below in the
> tip.xen[1] tree when merging the changes with 2.6.17-rc5, but will need a
> cleaner solution.

Ooops. Sorry.

I'll move linux-2.6-xen-sparse/include/asm-x86_64/e820.h to
linux-2.6-xen-sparse/include/asm-x86_64/mach-xen/asm/e820.h then the
native build will pickup the unmodified e820.h.

>   Also, the upstream changes make the i386 e820 changes
> less useful from the point of view of minimizing diffs from upstream.
> For dom0 why not use the machine map to start with?  I don't see the
> extra value of the two stage map.

The machine map contains the actual physical memory layout, which has no
relationship with the para-virtual layout, even in dom0.


Xen-devel mailing list

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