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] [PATCH] xen x86_64 and CONFIG_FLATMEM

To: Mark McLoughlin <markmc@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen x86_64 and CONFIG_FLATMEM
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 25 Jul 2006 15:36:19 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 25 Jul 2006 07:36:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1153304977.2769.19.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: <1153304977.2769.19.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 19 Jul 2006, at 11:29, Mark McLoughlin wrote:

        With CONFIG_SPARSEMEM on xen x86_64, you get an oops in mem_init where
it references mem_map; mem_map is only initialized with CONFIG_FLATMEM.

        Suggest a Kconfig change like the one attached?

Perhaps better to forcibly disable CONFIG_NUMA if CONFIG_XEN is enabled? We can't (yet) pick up NUMA info from Xen anyway, and it probably enables a bunch of code that hasn't been much tested on Xen.

 -- Keir

Xen-devel mailing list

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