Re: [PATCH 2/3] KVM: improve trace events of vmexit/mmio/ioport

[Avi Kivity]

On 01/17/2012 04:28 AM, Xiao Guangrong wrote:
> 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?
>

Why is it hard?  Correlate the task IDs.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/