linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Andrew Morton <akpm@osdl.org>, Jan Beulich <JBeulich@novell.com>,
	linux-kernel@vger.kernel.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	tony.luck@intel.com
Subject: Re: [PATCH] CONFIG_UNWIND_INFO
Date: 20 Jan 2006 07:13:57 +0100
Date: Fri, 20 Jan 2006 07:13:57 +0100	[thread overview]
Message-ID: <20060120061357.GA62569@muc.de> (raw)
In-Reply-To: <17360.27469.840898.303811@cargo.ozlabs.ibm.com>

On Fri, Jan 20, 2006 at 03:47:09PM +1100, Paul Mackerras wrote:
> Andi Kleen writes:
> 
> > 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.
> 
> Apparently the module loader loads all sections marked SHF_ALLOC,
> reasonably enough.
> 
> Why would we want the unwind tables in the .ko but not in kernel
> memory?  Isn't the point of this so that we can add an in-kernel
> unwinder?

For most people so far it was for kgdb where they would be needed
on disk only.

-Andi

      reply	other threads:[~2006-01-20  6:14 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
2006-01-18 16:48           ` Jan Beulich
2006-01-20  4:47       ` Paul Mackerras
2006-01-20  6:13         ` Andi Kleen [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=20060120061357.GA62569@muc.de \
    --to=ak@muc.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;
as well as URLs for NNTP newsgroup(s).