public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Paulo Marques <pmarques@grupopie.com>,
	Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
	Steven Rostedt <srostedt@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] kallsyms, tracing: output more proper symbol name
Date: Fri, 13 Mar 2009 20:40:13 +0100	[thread overview]
Message-ID: <20090313194013.GA23304@uranus.ravnborg.org> (raw)
In-Reply-To: <49BA2704.9040404@cn.fujitsu.com>

On Fri, Mar 13, 2009 at 05:27:32PM +0800, Lai Jiangshan wrote:
> Lai Jiangshan wrote:
> > Paulo Marques wrote:
> >> I would probably still place another test to compare the number of
> >> underscores, after both symbols are found to be equal in the "linker
> >> script provided" criteria.
> >>
> >> The way it is now, for my current kallsyms table:
> >>
> >>> ffffffff80200000 A _text
> >>> ffffffff80200000 T startup_64
> >>> ffffffff80209000 T _stext
> >>> ffffffff80209000 t init_post
> >> a "startup_64" address would display as "_text" and a "init_post"
> >> address would display as "_stext".
> >>
> >> You can add all the stext/etext symbols as special cases to the
> >> "may_be_linker_script_provide_symbol" function (like it was on your v1
> >> patch), but I'm just afraid that we'll find more cases in the future
> >> that are not automatically caught by these rules...
> >>
> > 
> 
> [resend, previous v3 has some mistakes]
> 
> Subject:  kallsyms, tracing: output more proper symbol name
> 
> Impact: bugfix, output reliable result
> 
> Debug tools(dump_stack(), ftrace...) are like to print out symbols.
> But it is always print out the first aliased symbol.(Aliased symbols
> are symbols with the same address), and the first aliased symbol is
> sometime not proper.
> 
> # echo function_graph > current_tracer
> # cat trace
> ......
>  1)   1.923 us    |    select_nohz_load_balancer();
>  1) + 76.692 us   |  }
>  1)               |  default_idle() {
>  1)   ==========> |    __irqentry_text_start() {
>  1)   0.000 us    |      native_apic_mem_write();
>  1)               |      irq_enter() {
>  1)   0.000 us    |        idle_cpu();
>  1)               |        tick_check_idle() {
>  1)   0.000 us    |          tick_check_oneshot_broadcast();
>  1)               |          tick_nohz_stop_idle() {
> ......
> 
> It's very embarrassing, it ouputs "__irqentry_text_start()",
> actually, it should output "smp_apic_timer_interrupt()".
> (these two symbol are the same address, but "__irqentry_text_start"
> is deemed to the first aliased symbol by scripts/kallsyms)
> 
> This patch puts symbols like "__irqentry_text_start" to the second
> aliased symbols. And a more proper symbol name becomes the first.
> 
> Aliased symbols mostly come from linker script. The solution is
> guessing "is this symbol defined in linker script", the symbols
> defined in linker script will not become the first aliased symbol.
> 
> And if symbols are found to be equal in this "linker script provided"
> criteria, symbols are sorted by the number of prefix underscores.
> 
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>

Looks good to me.

Acked-by: Sam Ravnborg <sam@ravnborg.org>

  parent reply	other threads:[~2009-03-13 19:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  9:37 [PATCH] kallsyms, tracing: output more proper symbol name Lai Jiangshan
2009-03-11  9:46 ` Ingo Molnar
2009-03-11 10:29   ` Frederic Weisbecker
2009-03-11 13:05   ` Paulo Marques
2009-03-12  2:43     ` Lai Jiangshan
2009-03-12 15:32       ` Paulo Marques
2009-03-13  7:10         ` [PATCH V3] " Lai Jiangshan
2009-03-13  9:27           ` Lai Jiangshan
2009-03-13 19:25             ` Paulo Marques
2009-03-13 19:40             ` Sam Ravnborg [this message]
2009-03-13 20:07               ` Andrew Morton
2009-03-13 20:34                 ` Paulo Marques
2009-03-14  8:54                 ` Ingo Molnar
2009-03-14  8:57           ` [tip:tracing/ftrace] " Lai Jiangshan

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=20090313194013.GA23304@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pmarques@grupopie.com \
    --cc=srostedt@redhat.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