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:
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.
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. Libpfm's example program self_smpl_multi seemed to do
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. Libpfm's example program self_smpl_multi seemed to do
something similar, so I rewrote it to take an arbitrary number of
