From: Pradeep Kumar Surisetty <psuriset@linux.vnet.ibm.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: KVM: perf: a smart tool to analyse kvm events
Date: Mon, 20 Feb 2012 15:50:29 +0530 [thread overview]
Message-ID: <20120220102029.GC8666@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F3DBCD8.2020505@linux.vnet.ibm.com>
* Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com> [2012-02-17 10:35:04]:
> On 02/16/2012 11:52 PM, Pradeep Kumar wrote:
>
> > Xiao,
> >
> > i tried your perf events patch set on RHEL 6.1 host and failed to trace kvm-events with below error message.
> >
> > [root@kvm perf]# ./perf kvm-events report
> > Warning: unknown op '{'
> > Warning: Error: expected type 5 but read 1
> > Warning: failed to read event print fmt for hrtimer_start
> > Warning: unknown op '{'
> > Warning: Error: expected type 5 but read 1
> > Warning: failed to read event print fmt for hrtimer_expire_entry
> > Analyze events for all VCPUs:
> > VM-EXIT Samples Samples% Time% Avg time
> > Total Samples:0, Total events handled time:0.00us.
> > [root@kvm perf]#
> >
>
>
> Thanks for your try, Pradeep!
>
> It seems that kvm events do not be recorded.
>
> Do your guest was running when kvm-events was executed?
Hello Xiao
my guest was not running when i executed.
> What is the output of "./perf script | grep kvm_*"?
[root@phx3 perf]# ./perf script | grep kvm_*
Warning: unknown op '{'
Warning: Error: expected type 5 but read 1
Warning: failed to read event print fmt for hrtimer_start
Warning: unknown op '{'
Warning: Error: expected type 5 but read 1
Warning: failed to read event print fmt for
hrtimer_expire_entry
# cmdline : /home/patch/linux/tools/perf/perf record -a -R
# -f -m 1024 -c 1 -e kvm:kvm_entry -e kvm:kvm_exit -e
# kvm:kvm_mmio -e kvm:kvm_pio -e timer:*
# event : name = kvm:kvm_entry, type = 2, config = 0x2ef,
# config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0,
# id = { 6241, 6242, 6243, 6244, 6245, 6246, 6247, 6248 }
# event : name = kvm:kvm_exit, type = 2, config = 0x2ea,
# config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0,
# id = { 6249, 6250, 6251, 6252, 6253, 6254, 6255, 6256 }
# event : name = kvm:kvm_mmio, type = 2, config = 0x2dd,
# config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0,
# id = { 6257, 6258, 6259, 6260, 6261, 6262, 6263, 6264 }
# event : name = kvm:kvm_pio, type = 2, config = 0x2ed,
# config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0,
# id = { 6265, 6266, 6267, 6268, 6269, 6270, 6271, 6272 }
no symbols found in /sbin/killall5, maybe install a debug
package?
--Pradeep
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-02-20 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 15:52 KVM: perf: a smart tool to analyse kvm events Pradeep Kumar
2012-02-17 2:35 ` Xiao Guangrong
2012-02-20 10:20 ` Pradeep Kumar Surisetty [this message]
2012-02-20 10:27 ` Xiao Guangrong
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=20120220102029.GC8666@linux.vnet.ibm.com \
--to=psuriset@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaoguangrong@linux.vnet.ibm.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 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.