All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Pradeep Kumar <psuriset@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: Fri, 17 Feb 2012 10:35:04 +0800	[thread overview]
Message-ID: <4F3DBCD8.2020505@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120216155248.6865.47935.sendpatchset@localhost.localdomain>

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?
What is the output of "./perf script | grep kvm_*"?

  reply	other threads:[~2012-02-17  2:35 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 [this message]
2012-02-20 10:20   ` Pradeep Kumar Surisetty
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=4F3DBCD8.2020505@linux.vnet.ibm.com \
    --to=xiaoguangrong@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psuriset@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.