mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: pmarques@grupopie.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_KALLSYMS_EXTRA_PASS
Date: Tue, 17 May 2005 20:00:51 -0400	[thread overview]
Message-ID: <1116374451.9737.47.camel@localhost.localdomain> (raw)
In-Reply-To: <1116372428.428a7dccec930@webmail.grupopie.com>

On Wed, 2005-05-18 at 00:27 +0100, pmarques@grupopie.com wrote:

> You can try the very crude (but effective) way to check if this is your problem
> or not. Go to scripts/kallsyms.c and change:
> 
> #define WORKING_SET             1024
> 
> to:
> 
> #define WORKING_SET             65536
> 

Yep, that did the trick. Thanks.  And just to make sure, I put it back
to 1024, recompiled, and got the error again.

> This will force kallsyms to use *all* the symbols for the compression, and the
> size of the result won't be affected by the symbol positions.
> 
> Don't forget to turn off KALLSYMS_EXTRA_PASS to test this.
> 
> If this turns out to be the problem _again_, I'll post a patch to fix this for
> good by storing the token data from the first pass and use it on the second
> pass. This will not only speed up compression, it will also guarantee that this
> kind of problems will never bite us again.

Your patch sounds too good to not be included even if this wasn't the
case. How come it hasn't been applied before?

-- Steve


  reply	other threads:[~2005-05-18  0:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 21:23 CONFIG_KALLSYMS_EXTRA_PASS Steven Rostedt
2005-05-17 23:27 ` CONFIG_KALLSYMS_EXTRA_PASS pmarques
2005-05-18  0:00   ` Steven Rostedt [this message]
2005-05-18  0:59     ` CONFIG_KALLSYMS_EXTRA_PASS pmarques

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=1116374451.9737.47.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.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

all inboxes | Powered by JetHome®