[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18990.64229.961985.491166@cargo.ozlabs.ibm.com>
Date: Wed, 10 Jun 2009 10:14:29 +1000
From: Paul Mackerras <paulus@...ba.org>
To: Corey Ashford <cjashfor@...ux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] perf_counter: extensible perf_counter_attr
Corey Ashford writes:
> Ok, some disclosure here: we have not yet supported either of these features in
> the Power PMU's in any open source code (and perhaps the proprietary code too,
> but I don't know about that). Since these features are described in an IBM
> proprietary document, I can't describe how they work here, except to say that
> they are present in the chip.
Actually, the public PPC970FX user manual has a chapter on the
performance monitor unit which describes both thresholding and the
instruction matching CAM, among other things.
I think we can support thresholding using higher-order bits of the
event code when the low bits == PM_THRESH_TIMEO. We can only have one
PM_THRESH_TIMEO event on the PMU at any given time, so there can't be
any conflict over the thresholder settings.
The IMC is more problematic, but we can't do much with it on POWER5
and later processors anyway, due to various things being accessible
only in hypervisor mode, so I have been ignoring it. :)
Paul.
--
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