From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH 2/3] KVM: improve trace events of vmexit/mmio/ioport
Date: Mon, 16 Jan 2012 11:38:03 +0200
Message-ID: <4F13EFFB.90706@redhat.com>
References: <4F13EE3D.2070602@linux.vnet.ibm.com> <4F13EE9B.9020901@linux.vnet.ibm.com>
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: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <4F13EE9B.9020901@linux.vnet.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

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