From: David Ahern <dsahern@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Wim Heirman" <wim@heirman.net>,
linux-kernel@vger.kernel.org,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: perf-stat per thread results
Date: Fri, 13 May 2011 09:41:06 -0600 [thread overview]
Message-ID: <4DCD5112.3020307@gmail.com> (raw)
In-Reply-To: <20110513153028.GC3854@elte.hu>
On 05/13/11 09:30, Ingo Molnar wrote:
> Yes perf record --stat should work. 'perf report -T --stdio' is supposed to
> print this, but it has regressed i think.
There is a known regression in 2.6.39; perf-record and perf-top cannot
profile all threads in a process. They fail with:
Fatal: failed to mmap with 22 (Invalid argument)
Curiously, perf-stat does work - or at least does not fail with the mmap
error.
David
>
> Arnaldo, any ideas?
>
> Thanks,
>
> Ingo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-05-13 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 15:14 perf-stat per thread results Wim Heirman
2011-05-13 15:30 ` Ingo Molnar
2011-05-13 15:41 ` David Ahern [this message]
2011-05-13 15:35 ` David Ahern
2011-05-13 15:44 ` Ingo Molnar
2011-05-13 20:32 ` Wim Heirman
2011-05-13 20:45 ` Arnaldo Carvalho de Melo
2011-05-14 12:45 ` Wim Heirman
2011-05-14 20:24 ` Wim Heirman
2011-05-13 23:02 ` David Ahern
2011-05-14 12:49 ` Wim Heirman
2011-05-14 17:48 ` David Ahern
2011-05-14 18:52 ` Wim Heirman
2011-05-14 18:57 ` David Ahern
2011-05-13 20:11 ` Juri Lelli
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=4DCD5112.3020307@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=wim@heirman.net \
/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).