> You're printing the thread ID, which is good. But, > suppose thre thread > in question gets re-scheduled on a different > processor (or hw thread). > > DTrace has a per-CPU trace log... You can see how > such re-ordering > might happen :)
I am lost, I thought the probe was enabled on all CPU's. 2009 Dec 18 19:45:31 thread 0x2a1065d9ca0 leaving -> this means thread 0x2a1065d9ca0 executed spa_sync:return and that thread's local variable "t" should be '0'. and the second spa_sync:enter has a predicate /self->t == 1 && self->prevtime > 0/ and should not run the 2nd spa_sync:enter unless the 1st spa_sync:enter runs in which case it should print "thread enter" message. Of-course I don't understand it well enough. Thanks for the time. -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
