Re: [PATCH] new kallsyms approach

[Andi Kleen <ak@suse.de>]

"Jan Beulich" <JBeulich@novell.com> writes:


> This patch provides al alternative to the pre-exisiting kallsyms code.
> That code, from a kernel debugger perspective at least, suffers from
> incomplete information, making it impossible to
> (a) disambiguate multiple static functions of the same name (in
> different
> source files),
> (b) determine a complete set of attributes for a symbol (namely, the
> symbol's size, but also its type, which gets converted to an nm-like
> one-
> character representation), and
> (c) retain full section information

I don't think it's a good idea to have two different ways
to do kallsyms. Either we should always use your new
way in standard KALLSYMS or not do it at all.

The major decision factor is how much bloat it adds.
Can you post before/after numbers of binary size? 

If the difference is >5% or so - are there ways to recover
the difference? 

-Andi