Displaying 5 results from an estimated 5 matches for "lwpsinfo_t".
2006 Jun 20
1
Extending lwpsinfo_t with pr_lgrp for DTrace consumers
The sched provider defines the stable "lgrp" variable that is the lgroup of
the current CPU. This is mostly interesting when we can compare it with the
actual thread home lgroup, so I''d like to extend the lwpsinfo_t structure with
the new pr_lgrp field which will be implemented using translator. This will
match the addition of the pr_lgrp field to the proc(4) lwpsinfo_t structure
that is done with the NUMA observability changes (it utilises one of the five
reserved fields).
The pr_lgrp field will only be a...
2006 Nov 16
6
DTrace hooks for CPU caps
..."wait queues" where threads may be placed to enforce caps.
I would like to make this visible through DTrace and to add two new probes to
the sched provider with the following semantics:
cpucaps-sleep Probe that fires immediately before the current thread is
placed on a wait queue. The lwpsinfo_t of the waiting thread is
pointed to by args[0]. The psinfo_t of the process containing
the waiting thread is pointed to by args[1].
cpucaps-wakeup Probe that fires immediately after a thread is removed
from a wait queue. The lwpsinfo_t of the waiting thread is pointed to
by args[0]. The ps...
2008 Feb 12
1
measuring sleep time in synchronization objects
...on output showed that the
threads in my program are sleeping on pr_stype = 3 (translates to SOBJ_CV
according to the file sobject.h). However, I was expecting to see the
threads sleeping on pr_stype = 5 (SOBJ_USER) as a result of sem_wait()
calls, because the description of pr_stype field in struct lwpsinfo_t says
that (and I quote from chapter 25 of the DTrace guide):
The pr_stype field is set when the thread is sleeping on a synchronization
object.
The possible values for the pr_stype field are:
SOBJ_MUTEX
SOBJ_RWLOCK
...
SOBJ_USER : A user-level synchronization object. All blocking on user-l...
2009 Sep 14
1
return from memset on mac osx
Does dtrace have a problem catching the return from memset on Mac OSX?
The script below catches the entry just fine but the return clause is
never entered.
Thanks, Joel
---
pid$target::memset:entry
/arg1 == 0/
{
self->size = arg2;
self->ts = timestamp;
self->vts = vtimestamp;
}
pid$target::memset:return
/self->size/
{
@ts = sum(timestamp - self->ts);
@vts =
2007 Nov 14
10
[GE users] Apple Leopard has dtrace -- anyone used the SGE probes/scripts yet?
Hi,
Chris (cc) and I try to get the SGE master monitor work with Apple Leopard
dtrace. Unfortunately we are stuck with the error msg below.
Anyone having an idea what could be the cause? What I can rule out as
cause is function inlining for the reasons explained below.
Background information on SGE master monitor implementation is under
http://wiki.gridengine.info/wiki/index.php/Dtrace