public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Akihiro Nagai <akihiro.nagai.hw@hitachi.com>,
	Ingo Molnar <mingo@elte.hu>,
	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 16:43:10 +0200	[thread overview]
Message-ID: <20110406144308.GF1867@nowhere> (raw)
In-Reply-To: <4D9C79F1.2060308@gmail.com>

On Wed, Apr 06, 2011 at 08:34:25AM -0600, David Ahern wrote:
> 
> 
> On 04/06/11 08:30, Frederic Weisbecker wrote:
> > On Wed, Apr 06, 2011 at 04:15:01PM +0200, Peter Zijlstra wrote:
> >> On Wed, 2011-04-06 at 11:09 -0300, Arnaldo Carvalho de Melo wrote:
> >>>> 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. 
> >>
> >> Huh, whot? You can get that using PERF_COUNT_SW_PAGE_FAULT and
> >> PERF_SAMPLE_ADDR.
> > 
> > Where are we doing that? I can't find the code that handles it.
> 
> That's what the other email thread was about, and the solution is just
> that - perf record -e faults -c 1 -d ... Then it comes to dumping the
> information. That's easy with the current perf-script.

Yeah indeed.

Thanks.

  reply	other threads:[~2011-04-06 14:43 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
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 [this message]
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=20110406144308.GF1867@nowhere \
    --to=fweisbec@gmail.com \
    --cc=2nddept-manager@sdl.hitachi.co.jp \
    --cc=acme@infradead.org \
    --cc=akihiro.nagai.hw@hitachi.com \
    --cc=dsahern@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