John,
Another possibility which I have not explored is to try pthread_kill() to
direct a signal
to the correct thread when received by the wrong thread. I don't know the
internals of
this call but from the definition, it may be the right thing to use.
On Fri, Jun 5, 2009 at 7:39 PM, john wrote:
PAPI isn't really a tool in itself. It's an API (library) at a somewhat
higher abstraction level than libpfm. It provides a set abilities that
are not in libpfm (without some sort of tool). For example, it provides
an API for profiling, scaling counts for multiplexed events, etc., and it
pro
Hi Stephane,
stephane eranian wrote:
> Hello John,
>
>
> On Fri, May 1, 2009 at 12:51 AM, john wrote:
>
>> Hello Stephane et al.,
>>
>> My goal is to have an arbitrary number of threads monitor themselves,
>> each being interrupted after approximately 1ms worth of clock cycles
>> have gone by.
Hi,
Probably not the correct terminology, but it may help if you view pfmon as a
"tool". You can, in fact, write your own tools (look under examples).
But as a tool writer, it would help if you have some APIs to help you access
the
hardware monitors. libpfm and perfmon (kernel) can provide this
