Stephane, Thanks for your replies. On Tuesday 04 September 2007 15:41, Stephane Eranian wrote: > Vivek,
> > Invalid Overflows=>If the SIGIO had fd (in siginfo structure) not meant > > for this thread. > > Well, I have seen this problem in the past even in per-thread mode. It was > reported on this list by U. of Waterloo. > > Did you do the F_SETSIG/F_SETOWN using gettid()? > Yes, i used gettid() when using F_SETSIG. > I think there maybe a problem with this approach because it seems hard > to guarantee which thread is going to receive the signal. Note that in > system-wide your monitoring program is probably doing nothing more than to > wait for the signal, in which case, it might as well, block on > read(fd,&msg). The workload you are running could as well run in a separate > program pinned to the core. > As suggested by you, I want to try out monitoring(of all the threads' events ) by a single thread . Do you have any example of the same ? I grepped for PFM_FL_NOTIFY_BLOCK (which I guess I would need to stop the thread which got overflow signal) and found that multiplex.c does trace some other process. Can you give me some example of how to do this with threads ? Specifically, how would an overflow signal (SIGIO which will be handled by master thread only) identify the thread for which it has come ? Regards, Vivek _______________________________________________ perfmon mailing list [email protected] http://www.hpl.hp.com/hosted/linux/mail-archives/perfmon/
