From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754218Ab0IFMt4 (ORCPT ); Mon, 6 Sep 2010 08:49:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42956 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751573Ab0IFMtz (ORCPT ); Mon, 6 Sep 2010 08:49:55 -0400 Message-ID: <4C84E35B.4090600@redhat.com> Date: Mon, 06 Sep 2010 15:49:31 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100806 Fedora/3.1.2-1.fc13 Lightning/1.0b2pre Thunderbird/3.1.2 MIME-Version: 1.0 To: Peter Zijlstra CC: linux-perf-users@vger.kernel.org, linux-kernel , Ingo Molnar Subject: Re: disabling group leader perf_event References: <4C84B088.5050003@redhat.com> <1283772256.1930.303.camel@laptop> <4C84D1CE.3070205@redhat.com> <1283774045.1930.341.camel@laptop> <4C84D77B.6040600@redhat.com> <1283776189.1930.380.camel@laptop> In-Reply-To: <1283776189.1930.380.camel@laptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/06/2010 03:29 PM, Peter Zijlstra wrote: > >>> So what you're basically trying to do is create some histogram of >>> exit_reason? >> Yes, exactly. > One thing I thought of, you can use the unfiltered kvm_exit event as > leader, that will give you the total number of events, which, esp. when > you create partial histograms, is useful to figure out how much you > missed. Yeah - and the aggregate kvm_exit count is the single most important metric for kvm. We do count it regardless of whether we want the individual exit_reasons or not. -- error compiling committee.c: too many arguments to function