lkml.org 
[lkml]   [2012]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2/3] KVM: improve trace events of vmexit/mmio/ioport
On 01/16/2012 05:38 PM, Avi Kivity wrote:

> On 01/16/2012 11:32 AM, Xiao Guangrong wrote:
>> - trace vcpu_id for these events
>
> We can infer the vcpu id from the kvm_entry tracepoints, no?
>


Thanks for your review, Avi!

Hmm. i think it is hard to do since the vcpu thread can be scheduled
anytime, one example is as follow:

CPU 0

kvm_entry vcpu 0
......
kvm_entry vcpu 1
......
event1 occurs
......
event2 occurs

It is hard to know the event belong to which kvm_entry?

>> - add kvm_mmio_done to trace the time when mmio/ioport emulation is completed
>
> ditto?
>


I think is ok to get the event end time by using kvm_entry.

>
> Relying on the existing tracepoints will make the tool work on older
> kernels.
>


We can drop all new events, but unfortunately, the information of the origin
tracepoints is not enough, at least vcpu_id need be traced in theses events
to match its events. Yes?



\
 
 \ /
  Last update: 2012-01-17 03:31    [W:0.055 / U:0.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site