Yes I think this is something I'm looking for, but I'm not sure if I can
use your Cap-Eye kernel image because my code changes are in kernel
modules such as ip, sockfs and genunix. Nevertheless, I'll be happy to
try it.
Unfortunately I touch a few areas in genunix so I don't think
you're going to be able to apply it here at the minute.
However, if you would like to try it out anyway, let me know
and I'll point you at the bits.
Jon.
- yxn
The following example shows user-land TLB activity by executable
on an Opteron processor. The probename in the probe specification
may well change but it consists of the event name followed the mode
specification and the count:
# dtrace -qn 'cpc:::[EMAIL PROTECTED] = count();}'
^C
dtrace 1
in.rlogind 1
ls 1
man 1
nroff 1
nscd 1
pt_chmod 1
quota 1
sh 1
sendmail 2
inetd 3
svc.configd 3
ksh 4
intrd 6
login 10
So, in the above we fire the probe every 1000 user-land TLB misses and
from there we simply aggregate on execname. In your case you would
simply change the mode/count to suit and aggregate on stack() (to
start with anyway). Note that we are not getting an absolute view of
event causation here but a sampled view; this should provide a
statistically valid picture of the event activity though.
I can happily provide you with a kernel to try but it comes as a
Cap-Eye and you, obviously, may not be able to use it if your bits
are outside of a single module or so.
Cheers.
Jon.
- yxn
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
