From: Gleb Natapov <gleb@redhat.com>
To: shashank rachamalla <shashank.rachamalla@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Questing regarding KVM Guest PMU
Date: Sun, 18 Mar 2012 16:50:45 +0200 [thread overview]
Message-ID: <20120318145045.GD27306@redhat.com> (raw)
In-Reply-To: <CAMONAZ5TEzoTK3+7aCbvtc20DuvmQVpt4Yq1jyaqrnkeAehecQ@mail.gmail.com>
On Sun, Mar 18, 2012 at 06:27:53PM +0530, shashank rachamalla wrote:
> 2012/3/18 Gleb Natapov <gleb@redhat.com>:
> > On Sun, Mar 18, 2012 at 03:48:53PM +0530, shashank rachamalla wrote:
> >>
> >> CPU: Core 2, speed 2200.19 MHz (estimated)
> >> Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a
> >> unit mask of 0x00 (Unhalted core cycles) count 100000
> >> CPU_CLK_UNHALT...|
> >> samples| %|
> >> ------------------
> >> 1 100.000 /no-vmlinux
> >>
> >>
> > What happens if you run "perf stat -e cycles a.out"?
>
> This is what i get when I run "perf stat ./a.out" ( with --cpu host
> passed in qemu-kvm )
>
> Performance counter stats for './a.out':
>
> 954.925996 task-clock-msecs # 0.955 CPUs
> 23 context-switches # 0.000 M/sec
> 0 CPU-migrations # 0.000 M/sec
> 93 page-faults # 0.000 M/sec
> 2110635735 cycles # 2210.261 M/sec
> 901816391 instructions # 0.427 IPC
> 247677 cache-references # 0.259 M/sec
> 15044 cache-misses # 0.016 M/sec
>
> 0.999846560 seconds time elapsed
>
> This is without --cpu host ( Note that only software events get monitored )
>
> Performance counter stats for './a.out':
>
> 913.826372 task-clock-msecs # 0.990 CPUs
> 13 context-switches # 0.000 M/sec
> 0 CPU-migrations # 0.000 M/sec
> 93 page-faults # 0.000 M/sec
> <not counted> cycles
> <not counted> instructions
> <not counted> cache-references
> <not counted> cache-misses
>
> 0.923182044 seconds time elapsed
>
> I guess things are working fine with perf. But why not with oprofile ?
>
Looks like it. I never tried oprofile. Will try to reproduce your
problem and see what oprofile is doing.
--
Gleb.
next prev parent reply other threads:[~2012-03-18 14:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 10:18 Questing regarding KVM Guest PMU shashank rachamalla
2012-03-18 10:30 ` Gleb Natapov
2012-03-18 12:57 ` shashank rachamalla
2012-03-18 14:50 ` Avi Kivity
2012-03-18 14:50 ` Gleb Natapov [this message]
2012-03-18 16:17 ` shashank rachamalla
2012-03-18 16:51 ` Gleb Natapov
2012-03-19 6:50 ` shashank rachamalla
2012-03-19 7:07 ` Gleb Natapov
2012-04-03 13:50 ` shashank rachamalla
2012-04-03 16:58 ` Gleb Natapov
2012-04-03 18:43 ` shashank rachamalla
2012-04-03 18:54 ` shashank rachamalla
2012-04-04 7:04 ` Gleb Natapov
2012-04-04 10:19 ` shashank rachamalla
2012-04-04 10:29 ` Gleb Natapov
2012-04-05 2:37 ` shashank rachamalla
2012-04-05 12:27 ` Avi Kivity
2012-04-05 12:37 ` Gleb Natapov
2012-04-05 12:48 ` Avi Kivity
2012-04-05 13:26 ` Gleb Natapov
2012-04-05 13:28 ` Avi Kivity
2012-04-05 13:48 ` Gleb Natapov
2012-04-05 13:57 ` Gleb Natapov
2012-04-05 14:38 ` Avi Kivity
2012-04-05 14:41 ` Gleb Natapov
2012-04-06 5:13 ` shashank rachamalla
2012-04-06 6:50 ` Gleb Natapov
2012-04-08 15:27 ` Gleb Natapov
2012-04-09 9:26 ` Gleb Natapov
2012-04-10 3:18 ` shashank rachamalla
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=20120318145045.GD27306@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=shashank.rachamalla@gmail.com \
/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