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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mark McLoughlin
2006-Jul-25 15:23 UTC
Re: [Xen-devel] [PATCH] xen x86_64 and CONFIG_FLATMEM
On Tue, 2006-07-25 at 15:36 +0100, Keir Fraser wrote:> 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.NUMA is already disabled if CONFIG_XEN is enabled. But SPARSEMEM can be enabled even without NUMA: config ARCH_SPARSEMEM_ENABLE def_bool y - depends on (NUMA || EXPERIMENTAL) + depends on (NUMA || EXPERIMENTAL) && !X86_64_XEN Cheers, Mark. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel