From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: tony.luck@intel.com,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Andrew Morton" <akpm@osdl.org>,
"Paul Mackerras" <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_UNWIND_INFO
Date: Wed, 18 Jan 2006 17:11:46 +0100 [thread overview]
Message-ID: <200601181711.47163.ak@suse.de> (raw)
In-Reply-To: <43CE73A0.76F0.0078.0@novell.com>
On Wednesday 18 January 2006 16:58, Jan Beulich wrote:
> >The module loader should be discarding these sections on most architectures
> >because there is nothing that needs them and it's just a waste of memory
> >to store them.
> >
> >[IA64 might be an exception because they have a kernel level unwinder]
> >
> >So it would be best to change the module loader to do this I guess.
>
> But that's why this is a config option: You can prevent the data from being created in the first place if you know you
> won't need it.
The usual use case is that you only need it on disk for your gdb,
but not in RAM. And it now even causes problems like the missing
relocations on PPC64.
[Yes NLKD is not "usual" right now, sorry]
At some point it will change for x86-64 at least when the NLKD unwinder
is ported into the kernel (which I plan to do), but even then it won't
be needed for majority of architectures. Since IA64 likely will need
an exception mechanism for this anyways x86-64 could then later use it too.
> For nlkd, adding code to discard these sections despite CONFIG_UNWIND_INFO would only make for more
> differences, because I'd then have to undo this discarding.
The interests of in tree usage normally beats caring for out of tree
patches.
-Andi
next prev parent reply other threads:[~2006-01-18 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 12:59 [PATCH] CONFIG_UNWIND_INFO Jan Beulich
2006-01-14 12:56 ` Andrew Morton
2006-01-14 14:03 ` Sam Ravnborg
2006-01-16 7:36 ` Jan Beulich
2006-01-16 7:46 ` Andrew Morton
2006-01-18 11:48 ` Paul Mackerras
2006-01-18 15:18 ` Andi Kleen
2006-01-18 15:58 ` Jan Beulich
2006-01-18 16:11 ` Andi Kleen [this message]
2006-01-18 16:48 ` Jan Beulich
2006-01-20 4:47 ` Paul Mackerras
2006-01-20 6:13 ` Andi Kleen
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=200601181711.47163.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tony.luck@intel.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