From: Mike Galbraith <efault@gmx.de>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf top: losing events?
Date: Thu, 21 Jan 2010 07:02:36 +0100 [thread overview]
Message-ID: <1264053756.26323.28.camel@marge.simson.net> (raw)
In-Reply-To: <1264052528.26323.13.camel@marge.simson.net>
Yup, definitely a booboo in there somewhere.
Step 1.
oinker running, perf top -C 3 -z
------------------------------------------------------------------------------------------------------------------------------
PerfTop: 1001 irqs/sec kernel: 0.0% [1000Hz cycles], (all, cpu: 3)
------------------------------------------------------------------------------------------------------------------------------
samples pcnt func DSO
_______ _____ ____ ______________
2003.00 100.0% main /root/bin/pert
perfect (off by one is beauty mark, not wart;)
Step 2.
taskset -c 3 ./massive_intr 3 999
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ P COMMAND
7133 root 20 0 7928 232 128 R 25 0.0 0:09.68 3 massive_intr
7134 root 20 0 7928 232 128 R 25 0.0 0:09.68 3 massive_intr
25932 root 20 0 7920 584 476 R 25 0.0 42:03.07 3 pert
7132 root 20 0 7928 232 128 R 25 0.0 0:09.68 3 massive_intr
------------------------------------------------------------------------------------------------------------------------------
PerfTop: 252 irqs/sec kernel: 0.8% [1000Hz cycles], (all, cpu: 3)
------------------------------------------------------------------------------------------------------------------------------
samples pcnt func DSO
_______ _____ ____ ______________
500.00 99.2% main /root/bin/pert
massive_intr appeared briefly, then poof, gone (likely when it forked
off worker-bees), leaving this.
-Mike
next prev parent reply other threads:[~2010-01-21 6:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 5:42 perf top: losing events? Mike Galbraith
2010-01-21 6:02 ` Mike Galbraith [this message]
2010-01-21 12:22 ` Arnaldo Carvalho de Melo
2010-01-21 14:28 ` Mike Galbraith
2010-01-21 14:49 ` Arnaldo Carvalho de Melo
2010-01-21 14:56 ` Mike Galbraith
2010-01-21 15:02 ` 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=1264053756.26323.28.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.