[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080720174456.55e41e8b@kopernikus.site>
Date: Sun, 20 Jul 2008 17:44:56 +0200
From: Bernhard Walle <bwalle@...e.de>
To: Bernhard Walle <bwalle@...e.de>
Cc: Dave Hansen <dave@...ux.vnet.ibm.com>,
Vegard Nossum <vegard.nossum@...il.com>,
Greg KH <gregkh@...e.de>,
Mariusz Kozlowski <m.kozlowski@...land.pl>,
Stephen Rothwell <sfr@...b.auug.org.au>,
kernel-testers@...r.kernel.org, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Ingo Molnar <mingo@...e.hu>, Vivek Goyal <vgoyal@...hat.com>,
kexec <kexec@...ts.infradead.org>
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068
trace_hardirqs_on_caller
* Bernhard Walle <bwalle@...e.de> [2008-07-20 15:03]:
>
> Because I didn't know that interface. And because I don't see that
> interface on my two systems that I just checked. i386 and x86-64. What
> do I have to do to enable that interface?
That interface depends on CONFIG_MEMORY_HOTPLUG. But given to that
dependency list,
128 config MEMORY_HOTPLUG
129 bool "Allow for memory hot-add"
130 depends on SPARSEMEM || X86_64_ACPI_NUMA
131 depends on HOTPLUG && !HIBERNATION && ARCH_ENABLE_MEMORY_HOTPLUG
132 depends on (IA64 || X86 || PPC64 || SUPERH || S390)
that interface is off on *many* systems (i386, x86_64), so we can't rely
on that interface in kexec. I think on POWER it's much more common than
on PC architectures.
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists