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: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [Xen-changelog] Convert x86/64 Linux to use the new memory map hypercall.
From: Chris Wright <chrisw@xxxxxxxxxxxx>
Date: Fri, 26 May 2006 11:29:25 -0700
Cc: Chris Wright <chrisw@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 26 May 2006 11:26:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1148639505.24768.41.camel@xxxxxxxxxxxxxxxxxxxxx>
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> <1148639505.24768.41.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/
* Ian Campbell (Ian.Campbell@xxxxxxxxxxxxx) wrote:
> 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.

I looked at that last night, but didn't see the
include/asm-x86_46/mach-xen/asm/ dir being used.
/me looks again
Ok, not sure how I missed it, was clearly past my bedtime ;-)

> >   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.

I was picturing a single sane map from the start.  So proper memory and
other resources.


Xen-devel mailing list

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