From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-arch@vger.kernel.org
Subject: Re: "N" symbols and System.map
Date: Fri, 05 Jun 2009 15:49:39 -0700 [thread overview]
Message-ID: <4A29A103.9050007@linux.intel.com> (raw)
In-Reply-To: <20090605223728.GP29008@uranus.ravnborg.org>
Sam Ravnborg wrote:
> On Fri, Jun 05, 2009 at 03:28:16PM -0700, H. Peter Anvin wrote:
>> Sam Ravnborg wrote:
>>> On Fri, May 01, 2009 at 03:24:18PM -0700, H. Peter Anvin wrote:
>>>> Hi all,
>>>>
>>>> right now, we filter out symbols that nm tag N, meaning "debugging
>>>> symbols", from System.map. However, at least on x86, the
>>>> linker-generated symbol _end is tagged N, and in fact is the only N in
>>>> the entire image.
>>>>
>>>> Are there other architectures which would suffer if N were included in
>>>> System.map, or would that be a reasonable thing to do?
>>> Peter - what is status here?
>>>
>>> Do you see _end tagged N with -tip?
>>> We landed a lot of changes to vmlinux.lds there.
>>>
>>> Needless to say I have not included N symbols for now.
>>>
>> I haven't checked it for a bit, as my immediate need for it disappeared,
>> but I don't think it's changed.
> We can revisit this if needed.
>
FWIW:
c43e0000 N _end
-hpa
prev parent reply other threads:[~2009-06-05 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 22:24 "N" symbols and System.map H. Peter Anvin
2009-05-01 22:39 ` Luck, Tony
2009-05-01 23:10 ` Andreas Schwab
2009-05-01 23:21 ` Sam Ravnborg
2009-05-02 0:00 ` H. Peter Anvin
2009-05-04 19:33 ` Sam Ravnborg
2009-05-04 19:33 ` Sam Ravnborg
2009-05-04 21:19 ` Andreas Schwab
2009-05-04 21:26 ` H. Peter Anvin
2009-05-04 21:39 ` Luck, Tony
2009-06-05 22:26 ` Sam Ravnborg
2009-06-05 22:28 ` H. Peter Anvin
2009-06-05 22:37 ` Sam Ravnborg
2009-06-05 22:49 ` H. Peter Anvin [this message]
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=4A29A103.9050007@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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