From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Wiki docs on counting and tracing KVM perf events Date: Thu, 13 May 2010 17:57:09 +0300 Message-ID: <4BEC1345.7040408@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm To: Stefan Hajnoczi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44107 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751575Ab0EMO5S (ORCPT ); Thu, 13 May 2010 10:57:18 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 05/13/2010 05:35 PM, Stefan Hajnoczi wrote: > How to count and trace KVM perf events: > > http://www.linux-kvm.org/page/Perf_events > > I want to draw attention to this because traditional kvm_stat and > kvm_trace use has been moving over to the debugfs based tracing > mechanisms. Perhaps we can flesh out documentation and examples of > common perf event usage. > > Two things are missing to make this really useful: - a continuously updating difference mode like kvm_stat - subevents; for example kvm:kvm_exit is an aggregate of all exit types that can be split using filters to show individual exit reason statistics The plan is to eventually remove kvm_stat based performance monitoring in favour of perf events. -- error compiling committee.c: too many arguments to function