From: David Ahern <dsahern@gmail.com>
To: wufei <at.wufei@gmail.com>, linux-perf-users@vger.kernel.org
Subject: Re: Found unknown events
Date: Mon, 04 Nov 2013 22:04:24 -0700 [thread overview]
Message-ID: <52787C58.7030100@gmail.com> (raw)
In-Reply-To: <CAGTy5_T+8sY4s+Lp6WhNwjtodqRJs2imd8i6_+7PvvnUf_zQnA@mail.gmail.com>
On 11/4/13, 7:40 AM, wufei wrote:
> Hello All,
>
> I am using perf to measure a multi-threaded program on kernel 3.2.23,
> the system has 40 cores and there are lots of context switches during
> the test. The command is:
> # perf record -e sched:sched_stat_sleep -e sched:sched_switch -e
> sched:sched_process_exit -g -r 0 -p 39249 sleep 5
> It generates a ~1GB size perf.data. `perf report` got 2 issues:
>
> 1. A lot of this warning message:
> Warning: Timestamp below last timeslice flush
What's the NUMA make up? multiple sockets?
>
> 2. No useful output, but this:
> Found 32117 unknown events!
Try increasing the mmap size. e.g., -m 2048. Does it decrease or remove
this stat?
David
next prev parent reply other threads:[~2013-11-05 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 14:40 Found unknown events wufei
2013-11-05 5:04 ` David Ahern [this message]
2013-11-05 6:44 ` wufei
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=52787C58.7030100@gmail.com \
--to=dsahern@gmail.com \
--cc=at.wufei@gmail.com \
--cc=linux-perf-users@vger.kernel.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