[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <493ECC48.6060107@nortel.com>
Date:	Tue, 09 Dec 2008 13:51:36 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	eranian@...il.com, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-arch@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Eric Dumazet <dada1@...mosbay.com>,
	Robert Richter <robert.richter@....com>,
	Arjan van de Veen <arjan@...radead.org>,
	Peter Anvin <hpa@...or.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Steven Rostedt <rostedt@...dmis.org>,
	David Miller <davem@...emloft.net>,
	Paul Mackerras <paulus@...ba.org>,
	Paolo Ciarrocchi <paolo.ciarrocchi@...il.com>
Subject: Re: [patch] Performance Counters for Linux, v2
Ingo Molnar wrote:
> * Chris Friesen <cfriesen@...tel.com> wrote:
>> Regardless of sampling method, don't you still want some way to 
>> enable/disable the various counters as close to simultaneously as 
>> possible?
> 
> If it's about counter control for the monitored task, then we sure could 
> do something about that. (apps/libraries could thus select a subset of 
> functions to profile/measure, runtime, etc.)
> 
> If it's about counter control for the profiler/debugger, i'm not sure how 
> useful that is - do you have a good usecase for it?
I'm sure that others could give more usecases, but I was thinking about 
cases like "I want to test _these_ multiple metrics simultaneously over 
_this_ specific section of code".  In a case like this, it seems 
desirable to start/stop the various performance counters as close 
together as possible, especially if the section of code being tested is 
short.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
