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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

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

ditto?


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


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

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux