From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] KVM: VMX: add tracepoint for vpids
Date: Mon, 12 Mar 2012 12:34:40 +0200
Message-ID: <4F5DD140.7040605@redhat.com>
References: <1331481472.17316.1.camel@offbook> <4F5DB245.9060205@redhat.com> <1331551781.1334.3.camel@offworld>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
To: Davidlohr Bueso <dave@gnu.org>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <1331551781.1334.3.camel@offworld>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

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@gnu.org>
> > >
> > > 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