From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-perf-users@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC PATCH] perf tui: Annotate entries in callchains
Date: Fri, 20 Mar 2015 18:45:42 -0300 [thread overview]
Message-ID: <20150320214542.GS16485@kernel.org> (raw)
In-Reply-To: <20150320213429.GR16485@kernel.org>
Em Fri, Mar 20, 2015 at 06:34:29PM -0300, Arnaldo Carvalho de Melo escreveu:
> Strange, are you pressing 'V' on the main 'perf record' view, i.e. before
> getting to the annotation browser, to see the DSO just after the symbol?
>
> Trying with a deeper callchain in pow-me-harder.c...
I'm not being able to reproduce this, out of ideas, back to processing
some other patches, please let me know about any news on your side :-\
- Arnaldo
next prev parent reply other threads:[~2015-03-20 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 22:58 [RFC PATCH] perf tui: Annotate entries in callchains Arnaldo Carvalho de Melo
2015-03-20 0:34 ` Stephane Eranian
[not found] ` <CA+JHD93s2VkkdJMKZOGa6fPwEd43C8Ow80CU0b=bwTV=_8zjhw@mail.gmail.com>
2015-03-20 17:15 ` Stephane Eranian
2015-03-20 17:21 ` Arnaldo Carvalho de Melo
2015-03-20 20:39 ` Arnaldo Carvalho de Melo
2015-03-20 21:07 ` Arnaldo Carvalho de Melo
2015-03-20 21:12 ` Stephane Eranian
2015-03-20 21:34 ` Arnaldo Carvalho de Melo
2015-03-20 21:45 ` Arnaldo Carvalho de Melo [this message]
2015-03-23 0:27 ` Namhyung Kim
2015-03-23 16:49 ` Stephane Eranian
2015-03-23 16:56 ` Arnaldo Carvalho de Melo
2015-03-27 23:05 ` Stephane Eranian
2015-03-28 16:24 ` Arnaldo Carvalho de Melo
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=20150320214542.GS16485@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).