[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081210034824.GA27217@linux-sh.org>
Date: Wed, 10 Dec 2008 12:48:24 +0900
From: Paul Mundt <lethal@...ux-sh.org>
To: David Miller <davem@...emloft.net>
Cc: andi@...stfloor.org, mingo@...e.hu, a.p.zijlstra@...llo.nl,
paulus@...ba.org, tglx@...utronix.de, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, akpm@...ux-foundation.org,
eranian@...glemail.com, dada1@...mosbay.com,
robert.richter@....com, arjan@...radead.org, hpa@...or.com,
rostedt@...dmis.org
Subject: Re: [patch 0/3] [Announcement] Performance Counters for Linux
On Fri, Dec 05, 2008 at 12:08:14PM -0800, David Miller wrote:
> From: Andi Kleen <andi@...stfloor.org>
> Date: Fri, 05 Dec 2008 13:39:43 +0100
>
> > Given these are more obscure features, but not being able to fit
> > them easily into your model from the start isn't a very promising sign
> > for the long term extensibility of the design.
>
> Another thing I'm interested in is if this new stuff will work with
> performance counters that lack an overflow interrupt.
>
> We have several chips that are like this, and perfmon supported that
> on the kernel side, and also provided overflow emulation for such
> hardware in userspace (where such complexity belongs).
There doesn't seem to have been any reply to this point unfortunately,
and it is something I am also wondering about.
The sh perf counters were not designed with overflowing in mind, they are
split in to a pair of 48-bit or 64-bit counters that simply keep running.
Any write simply clears the value and the counter starts over. They are
simply counters only, and generate no events whatsoever.
Oprofile has been a pretty bad fit for them, and while I'm slightly more
optimistic about perfmon, I'm rather less enthusiastic about yet another
peformance counter implementation that I am unable to make any use of.
--
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