Re: KVM: perf: a smart tool to analyse kvm events

Re: KVM: perf: a smart tool to analyse kvm events

[Pradeep Kumar]

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]#          
	     
    --Pradeep

Re: KVM: perf: a smart tool to analyse kvm events

[Xiao Guangrong]

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_*"?

Re: KVM: perf: a smart tool to analyse kvm events

[Pradeep Kumar Surisetty]

* 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
> 

Re: KVM: perf: a smart tool to analyse kvm events

[Xiao Guangrong]

On 02/20/2012 06:20 PM, Pradeep Kumar Surisetty wrote:

> * 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. 
> 


kvm-events only analyse kvm events and this events are generated only when
kvm guest is running. :)

>> 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?
> 


That means no kvm event is recorded, please try it again when
your kvm guest is running.

Thanks, Pradeep!