From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: David Ahern <dsahern@gmail.com>,
Akihiro Nagai <akihiro.nagai.hw@hitachi.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
2nddept-manager@sdl.hitachi.co.jp,
Paul Mackerras <paulus@samba.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH -tip v3 3/6] perf branch trace: print pid and command
Date: Wed, 6 Apr 2011 11:09:58 -0300 [thread overview]
Message-ID: <20110406140958.GA4987@ghostprotocols.net> (raw)
In-Reply-To: <20110406121501.GA1867@nowhere>
Em Wed, Apr 06, 2011 at 02:15:07PM +0200, Frederic Weisbecker escreveu:
> On Fri, Apr 01, 2011 at 11:11:10AM -0600, David Ahern wrote:
> > On 04/01/11 09:13, Frederic Weisbecker wrote:
> > > But well, we can start simple and make and just do the => trick
> > > if we have PERF_SAMPLE_ADDR and resolve addr if the user asked
> > > the sym. Then when we have the graph output, have these per evsel
> > > display callbacks.
> > There is another email thread about page faults. The user wants sample
> > address resolved to symbols. I was going to look into it next week when
> > I get back from vacation.
> What we seem to need for that is to bring a pagefault tracepoint. We had
> propositions for that in the past, but work on this is in pause mode it
> seems.
Isn't there one in the 'tip/tmp.perf/trace' tmp branch? Lemme see...
Yeah, and it is even yours ;-)
commit 6a824e89c0dfe6bce3d7e85f987ec9c8e7304b34
Author: Frederic Weisbecker <fweisbec@gmail.com>
Date: Fri Nov 12 05:35:06 2010 +0100
perf, mm: Add fault tracing
Part of that are two modified patches from Jiri Olsa who added the
fault tracepoints. I had to split them in two tracepoints so that we get
the faults handling duration.
Originally-from: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Can we dust this one off and get the ball rolling again?
- Arnaldo
next prev parent reply other threads:[~2011-04-06 14:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 11:31 [PATCH -tip v3 0/6] perf: Introduce branch sub commands Akihiro Nagai
2011-03-24 11:31 ` [PATCH -tip v3 1/6] perf: new subcommand perf branch record Akihiro Nagai
2011-03-24 11:32 ` [PATCH -tip v3 2/6] perf branch: Introduce new sub command 'perf branch trace' Akihiro Nagai
2011-03-24 11:32 ` [PATCH -tip v3 3/6] perf branch trace: print pid and command Akihiro Nagai
2011-03-24 17:05 ` David Ahern
2011-03-25 10:14 ` Akihiro Nagai
2011-03-25 15:02 ` David Ahern
2011-03-28 10:34 ` Akihiro Nagai
2011-03-28 14:31 ` David Ahern
2011-04-01 15:13 ` Frederic Weisbecker
2011-04-01 15:15 ` Peter Zijlstra
2011-04-01 15:24 ` Arnaldo Carvalho de Melo
2011-04-01 17:11 ` David Ahern
2011-04-01 20:20 ` Peter Zijlstra
2011-04-06 12:15 ` Frederic Weisbecker
2011-04-06 14:09 ` Arnaldo Carvalho de Melo [this message]
2011-04-06 14:15 ` Peter Zijlstra
2011-04-06 14:30 ` Frederic Weisbecker
2011-04-06 14:34 ` David Ahern
2011-04-06 14:43 ` Frederic Weisbecker
2011-04-06 14:42 ` Frederic Weisbecker
2011-04-06 14:55 ` Frederic Weisbecker
2011-04-06 17:18 ` Arnaldo Carvalho de Melo
2011-04-04 10:00 ` Akihiro Nagai
2011-04-06 12:52 ` Frederic Weisbecker
2011-04-11 4:54 ` Akihiro Nagai
2011-03-24 11:32 ` [PATCH -tip v3 4/6] perf branch trace: print file path of the executed elf Akihiro Nagai
2011-03-24 11:32 ` [PATCH -tip v3 5/6] perf branch trace: print function+offset Akihiro Nagai
2011-03-24 11:32 ` [PATCH -tip v3 6/6] perf branch trace: add print all option Akihiro Nagai
2011-03-30 14:46 ` [PATCH -tip v3 0/6] perf: Introduce branch sub commands Frederic Weisbecker
2011-04-01 10:57 ` Akihiro Nagai
2011-04-01 12:51 ` Frederic Weisbecker
2011-04-01 14:43 ` Frederic Weisbecker
2011-04-04 10:06 ` Akihiro Nagai
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=20110406140958.GA4987@ghostprotocols.net \
--to=acme@infradead.org \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=akihiro.nagai.hw@hitachi.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.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