[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090514170211.GA5129@linux-sh.org>
Date: Fri, 15 May 2009 02:02:11 +0900
From: Paul Mundt <lethal@...ux-sh.org>
To: Johannes Weiner <hannes@...xchg.org>
Cc: Mel Gorman <mel@....ul.ie>, akpm@...ux-foundation.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
hartleys@...ionengravers.com, mcrapet@...il.com,
linux@....linux.org.uk, fred99@...olina.rr.com,
linux-arm-kernel@...ts.arm.linux.org.uk,
Badari Pulavarty <pbadari@...ibm.com>,
Yasunori Goto <y-goto@...fujitsu.com>
Subject: Re: [PATCH] Double check memmap is actually valid with a memmap has unexpected holes
On Wed, May 06, 2009 at 05:50:43PM +0200, Johannes Weiner wrote:
> On Wed, May 06, 2009 at 03:31:00PM +0100, Mel Gorman wrote:
> > As it turns out, ARM has its own show_mem(). I don't see how, but ARM
> > must not be using lib/show_mem.c even though it compiles it.
>
> It's some linker magic for lib/. It compiles both but treats the
> library version as weak symbol (or something).
>
This is true for lib-y handling in general, which lib/show_mem.o falls
under. Much of lib/ is obj-y though due to the fact that EXPORT_SYMBOL's
from lib-y are ineffective (people seem to get bitten by this at least
once a week), as a result, many things that start out as lib-y are
gradually moved over to obj-y, meaning that __weak annotations in obj-y
objects start to take precedent over lib-y magic anyways.. :-)
--
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