From: Paul Mundt <lethal@linux-sh.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Mel Gorman <mel@csn.ul.ie>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, hartleys@visionengravers.com,
mcrapet@gmail.com, linux@arm.linux.org.uk,
fred99@carolina.rr.com, linux-arm-kernel@lists.arm.linux.org.uk,
Badari Pulavarty <pbadari@us.ibm.com>,
Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: Re: [PATCH] Double check memmap is actually valid with a memmap has unexpected holes
Date: Fri, 15 May 2009 02:02:11 +0900 [thread overview]
Message-ID: <20090514170211.GA5129@linux-sh.org> (raw)
In-Reply-To: <20090506155043.GA3084@cmpxchg.org>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-05-14 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 8:29 [PATCH] Double check memmap is actually valid with a memmap has unexpected holes Mel Gorman
2009-05-05 8:36 ` Russell King - ARM Linux
2009-05-05 8:49 ` Mel Gorman
2009-05-13 16:34 ` [PATCH] Double check memmap is actually valid with a memmap has unexpected holes V2 Mel Gorman
2009-05-13 19:48 ` Andrew Morton
2009-05-14 8:39 ` Mel Gorman
2009-05-17 16:27 ` Russell King - ARM Linux
2009-05-05 11:06 ` [PATCH] Double check memmap is actually valid with a memmap has unexpected holes Johannes Weiner
2009-05-06 14:31 ` Mel Gorman
2009-05-06 15:50 ` Johannes Weiner
2009-05-07 5:29 ` Yasunori Goto
2009-05-14 17:02 ` Paul Mundt [this message]
2009-05-06 19:20 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090514170211.GA5129@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=fred99@carolina.rr.com \
--cc=hannes@cmpxchg.org \
--cc=hartleys@visionengravers.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=mcrapet@gmail.com \
--cc=mel@csn.ul.ie \
--cc=pbadari@us.ibm.com \
--cc=y-goto@jp.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).