From: Mark McLoughlin Subject: [PATCH] xen x86_64 and CONFIG_FLATMEM Date: Wed, 19 Jul 2006 11:29:37 +0100 Message-ID: <1153304977.2769.19.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-TGGbfxrdR7UYLtmtra7T" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --=-TGGbfxrdR7UYLtmtra7T Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi, 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? Cheers, Mark. --=-TGGbfxrdR7UYLtmtra7T Content-Disposition: attachment; filename=xen-flatmem-kconfig.patch Content-Type: text/x-patch; name=xen-flatmem-kconfig.patch; charset=UTF-8 Content-Transfer-Encoding: 7bit diff -r ecb8ff1fcf1f linux-2.6-xen-sparse/arch/x86_64/Kconfig --- a/linux-2.6-xen-sparse/arch/x86_64/Kconfig Fri Jul 14 18:53:27 2006 +0100 +++ b/linux-2.6-xen-sparse/arch/x86_64/Kconfig Wed Jul 19 11:28:59 2006 +0100 @@ -330,7 +330,7 @@ config ARCH_DISCONTIGMEM_DEFAULT config ARCH_SPARSEMEM_ENABLE def_bool y - depends on (NUMA || EXPERIMENTAL) + depends on (NUMA || EXPERIMENTAL) && !X86_64_XEN config ARCH_MEMORY_PROBE def_bool y --=-TGGbfxrdR7UYLtmtra7T Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --=-TGGbfxrdR7UYLtmtra7T--