On 03/13/2012 12:58 PM, Davidlohr Bueso wrote:
> On Mon, 2012-03-12 at 12:34 +0200, Avi Kivity wrote:
> > 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
On Mon, 2012-03-12 at 12:34 +0200, Avi Kivity wrote:
> 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
> > > >
> > > > Add a new tracepoint for vpid allocation
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
> > >
> > > Add a new tracepoint for vpid allocation and freeing associated to all
> > > vCPUs.
> > >
> >
> > Why?
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
> >
> > 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
On 03/11/2012 05:57 PM, Davidlohr Bueso wrote:
> From: Davidlohr Bueso
>
> Add a new tracepoint for vpid allocation and freeing associated to all vCPUs.
>
Why?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list:
From: Davidlohr Bueso
Add a new tracepoint for vpid allocation and freeing associated to all vCPUs.
Signed-off-by: Davidlohr Bueso
---
arch/x86/kvm/trace.h | 23 +++
arch/x86/kvm/vmx.c |5 -
arch/x86/kvm/x86.c |1 +
3 files changed, 28 insertions(+), 1 del
