Re: [PATCH] KVM: VMX: add tracepoint for vpids

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

 



On 03/12/2012 01:29 PM, Davidlohr Bueso wrote:
> On Mon, 2012-03-12 at 10:22 +0200, Avi Kivity wrote:
> > On 03/11/2012 05:57 PM, Davidlohr Bueso wrote:
> > > From: Davidlohr Bueso <dave@xxxxxxx>
> > >
> > > Add a new tracepoint for vpid allocation and freeing associated to all vCPUs.
> > >
> > 
> > Why?
> > 
>
> We have been using this tracepoint for some time now to help debug vpids
> and simulating tagged TLB behavior and performance. This gets to be non
> trivial when working with large amounts of guests and vCPUs.

I don't follow.  Can you give an example of when this tracepoint would
be useful?

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