[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1195208633.3059.7.camel@twins>
Date: Fri, 16 Nov 2007 11:23:53 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: David Miller <davem@...emloft.net>, clameter@....com,
akpm@...ux-foundation.org, linux-mm@...r.kernel.org,
linux-kernel@...r.kernel.org, dada1@...mosbay.com,
schwidefsky@...ibm.com, Ingo Molnar <mingo@...e.hu>
Subject: large lockdep bss (was: Re: [patch 01/28] cpu alloc: The allocator)
On Wed, 2007-11-14 at 03:28 +0100, Andi Kleen wrote:
> On Tue, Nov 13, 2007 at 05:52:08PM -0800, David Miller wrote:
> > Yes, I've run into similar problems with lockdep as well.
> > I had to build an ultra minimalized kernel to get it to
> > boot on my Niagara boxes.
> >
> > I think I even looked at the same lockdep code, and I'd
> > appreciate it if you'd submit your fix for this if you
> > haven't already.
>
> ftp://firstfloor.org/pub/ak/x86_64/quilt/patches/early-reserve
> ftp://firstfloor.org/pub/ak/x86_64/quilt/patches/early-alloc
> ftp://firstfloor.org/pub/ak/x86_64/quilt/patches/lockdep-early-alloc
>
> I didn't plan to submit it for .24, just .25. Or do you need it
> urgently?
>
> Also it would require you to write a sparc specific arch_early_alloc()
> of course. I've only done the x86-64 version.
Would've been nice to have heard about this lockdep problem. Anyway,
thanks for tackling it.
How about moving this bit:
+#ifndef ARCH_HAS_EARLY_ALLOC
+#define LARGEVAR(x,y) { static typeof(*x) __ ## x[y]; x = __ ## x; }
+#else
+#define LARGEVAR(x,y) x = arch_early_alloc(sizeof(*x) * y)
+#endif
out of the lockdep code and into the generic early alloc code?
-
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