From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933497Ab3BLR3x (ORCPT ); Tue, 12 Feb 2013 12:29:53 -0500 Received: from mga01.intel.com ([192.55.52.88]:35561 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932348Ab3BLR3w (ORCPT ); Tue, 12 Feb 2013 12:29:52 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,650,1355126400"; d="scan'208";a="290162340" Date: Tue, 12 Feb 2013 09:29:51 -0800 From: Andi Kleen To: Stephane Eranian Cc: LKML , Peter Zijlstra , "mingo@elte.hu" , Arnaldo Carvalho de Melo , Jiri Olsa , Namhyung Kim Subject: Re: [PATCH 0/2] perf stat: add per-core count aggregation Message-ID: <20130212172951.GD30387@tassilo.jf.intel.com> References: <1360678168-6974-1-git-send-email-eranian@google.com> <20130212172319.GB30387@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > > The idea itself is useful. > > > Yes, it is. BTW it would be even more useful if it could print some of the statistics turbostat does (in particular frequency and C0 residency) Often you only care about cycles not idle, and the frequency tells you how fast the cycles happen. I think Cx could be added relatively easily as a software event, but frequency doesn't fit very well into the perf counting model, as it's really sampling. -Andi