From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [patch] Performance Counters for Linux, v2 Date: Tue, 9 Dec 2008 14:00:45 +0100 Message-ID: <20081209130045.GA32479@elte.hu> References: <20081208012211.GA23106@elte.hu> <18748.37739.383961.318233@drongo.ozlabs.ibm.com> <20081208113318.GA14723@elte.hu> <18749.39345.732524.905159@cargo.ozlabs.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:36610 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751894AbYLINBH (ORCPT ); Tue, 9 Dec 2008 08:01:07 -0500 Content-Disposition: inline In-Reply-To: <18749.39345.732524.905159@cargo.ozlabs.ibm.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Paul Mackerras Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , linux-arch@vger.kernel.org, Andrew Morton , Stephane Eranian , Eric Dumazet , Robert Richter , Arjan van de Veen , Peter Anvin , Peter Zijlstra , Steven Rostedt , David Miller * Paul Mackerras wrote: > > Things like: "kerneltop would not be as accurate with: ..., to the > > level of adding 5% of extra noise.". Would that work for you? > > OK, here's an example. I have an application whose execution has > several different phases, and I want to measure the L1 Icache hit rate > and the L1 Dcache hit rate as a function of time and make a graph. So > I need counters for L1 Icache accesses, L1 Icache misses, L1 Dcache > accesses, and L1 Dcache misses. I want to sample at 1ms intervals. The > CPU I'm running on has two counters. > > With your current proposal, I don't see any way to make sure that the > counter scheduler counts L1 Dcache accesses and L1 Dcache misses at the > same time, then schedules L1 Icache accesses and L1 Icache misses. I > could end up with L1 Dcache accesses and L1 Icache accesses, then L1 > Dcache misses and L1 Icache misses - and get a nonsensical situation > like the misses being greater than the accesses. yes, agreed, this is a valid special case of simple counter readout - we'll add support to couple counters like that. Note that this issue does not impact use of multiple counters in profilers. (i.e. anything that is not a pure readout of the counter, along linear time, as your example above suggests). Once we start sampling the context, grouping of counters becomes irrelevant (and a hindrance) and static frequency sampling becomes an inferior method of sampling. ( The highest quality statistical approach is the kind of multi-counter sampling model you can see implemented in KernelTop for example, where the counters are independently sampled. Can go on in great detail about this if you are interested - this is the far more interesting usecase in practice. ) Ingo