From: Paulo Marques <pmarques@grupopie.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: inconsistent kallsyms data [2.6.11-mm2]
Date: Wed, 09 Mar 2005 20:16:35 +0000 [thread overview]
Message-ID: <422F59A3.9010209@grupopie.com> (raw)
In-Reply-To: <422EF2B0.7070304@grupopie.com>
Paulo Marques wrote:
> [...]
> Can you send me privately a tar.bz2 containing your .config,
> .tmp_kallsyms1.S and .tmp_kallsyms2.S so I can try to figure out what's
> going on?
Ok, after some investigation into the files I was able to find out the
problem.
scripts/kallsyms.c uses a subset of the symbol table to optimize the
tokens to use to compress the symbols. It does this because using the
complete set of symbols would be much slower without a significant gain
in compression.
For some reason, in the files sent by Dominik, two aliased symbols
change places from the first to the second step of the kallsyms build
process (__sched_text_start, __down).
Because of this, the subset used for optimization is different and so
are the tokens selected, producing a 2 byte difference in the total size
of the compressed symbol names :P
So I must change the sampling algorithm in a way that is robust to
symbol position changes.
A simple and robust way is to do the sampling on a list of symbols
sorted by symbol name. This way, even if the symbol positions that are
given to scripts/kallsyms change, the symbols sampled will be the same.
I'll do the patch to do this and send it ASAP.
--
Paulo Marques - www.grupopie.com
All that is necessary for the triumph of evil is that good men do nothing.
Edmund Burke (1729 - 1797)
next prev parent reply other threads:[~2005-03-09 21:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 11:38 2.6.11-mm2 Andrew Morton
2005-03-08 13:58 ` 2.6.11-mm2 Paul Mundt
2005-03-08 19:40 ` 2.6.11-mm2 Andrew Morton
2005-03-08 16:00 ` 2.6.11-mm2 (compile stats) John Cherry
2005-03-08 18:54 ` 2.6.11-mm2 fremap.c compile error Jurriaan
2005-03-11 22:50 ` Adrian Bunk
2005-03-08 19:29 ` inconsistent kallsyms data [2.6.11-mm2] Dominik Brodowski
2005-03-08 20:35 ` Andrew Morton
2005-03-08 20:45 ` Dominik Brodowski
2005-03-09 12:57 ` Paulo Marques
2005-03-09 20:16 ` Paulo Marques [this message]
2005-03-10 12:12 ` Paulo Marques
2005-03-13 8:54 ` Sam Ravnborg
2005-03-14 13:33 ` Paulo Marques
2005-03-14 22:17 ` Dominik Brodowski
2005-03-14 22:14 ` Dominik Brodowski
2005-03-08 23:20 ` 2.6.11-mm2 Christoph Hellwig
2005-03-08 23:29 ` 2.6.11-mm2 Andrew Morton
2005-03-08 23:36 ` 2.6.11-mm2 J.A. Magallon
2005-03-08 23:44 ` 2.6.11-mm2 Robert Love
2005-03-08 23:51 ` 2.6.11-mm2 J.A. Magallon
2005-03-09 0:02 ` 2.6.11-mm2 Robert Love
2005-03-09 0:16 ` 2.6.11-mm2 Adrian Bunk
2005-03-09 0:53 ` 2.6.11-mm2 Andrew Morton
2005-03-09 1:39 ` 2.6.11-mm2 Jeff Garzik
2005-03-09 0:20 ` 2.6.11-mm2 Adrian Bunk
2005-03-09 1:50 ` 2.6.11-mm2 Karsten Keil
2005-03-10 7:57 ` 2.6.11-mm2 Stefano Rivoir
[not found] ` <422FFDEF.2060706-g1Oybe70Lz0@public.gmane.org>
2005-03-10 8:09 ` 2.6.11-mm2 Andrew Morton
2005-03-10 8:09 ` 2.6.11-mm2 Andrew Morton
2005-05-25 22:43 ` 2.6.11-mm2 Andrew Morton
[not found] ` <20050525154308.57cde7ab.akpm-3NddpPZAyC0@public.gmane.org>
2005-05-26 17:43 ` 2.6.11-mm2 Stefano Rivoir
2005-03-21 23:45 ` 2.6.11-mm2 Andrew Morton
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=422F59A3.9010209@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.