All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	peterz@infradead.org, fweisbec@gmail.com, paulus@samba.org,
	tglx@linutronix.de, Akihiro Nagai <akihiro.nagai.hw@hitachi.com>
Subject: Re: [PATCH] perf script: fix regression in dso name
Date: Wed, 30 May 2012 14:27:24 -0300	[thread overview]
Message-ID: <20120530172724.GC12477@infradead.org> (raw)
In-Reply-To: <1338353906-60706-1-git-send-email-dsahern@gmail.com>

Em Tue, May 29, 2012 at 10:58:26PM -0600, David Ahern escreveu:
> $ perf script -i /tmp/perf.data
> ...
> gcc 13623 544315.062858: context-switches:
>     ffffffff815f65c9 __schedule ([kernel.kallsyms])
>     ffffffff81087cea __cond_resched ([kernel.kallsyms])
>     ffffffff815f6b92 _cond_resched ([kernel.kallsyms])
>     ffffffff815fb87a do_page_fault ([kernel.kallsyms])
>     ffffffff815f8465 page_fault ([kernel.kallsyms])
>         2b7a71ea0303 _dl_lookup_symbol_x ([kernel.kallsyms])
>         2b7a71ea1eb5 _dl_relocate_object ([kernel.kallsyms])
>         2b7a71e99b2e dl_main ([kernel.kallsyms])
>         2b7a71eab7f4 _dl_sysdep_start ([kernel.kallsyms])
> 
> All DSO's in a callchain are printed as [kernel.kallsyms].

Thanks, reproduced, tested and pushed to perf/urgent.

Unfortunately saw this after the last pull req, will include it in the
next if Ingo pulls from the signed tag instead of perf/urgent.

- Arnaldo

  reply	other threads:[~2012-05-30 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  4:58 [PATCH] perf script: fix regression in dso name David Ahern
2012-05-30 17:27 ` Arnaldo Carvalho de Melo [this message]
2012-05-30 17:32   ` David Ahern
2012-06-06  6:58 ` [tip:perf/urgent] perf script: Fix regression in callchain " tip-bot for David Ahern

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=20120530172724.GC12477@infradead.org \
    --to=acme@ghostprotocols.net \
    --cc=akihiro.nagai.hw@hitachi.com \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.