Re: [dtrace-discuss] matching the -module-
Do these post have some connection to the thread topic? BTW. the mdb settings recommended by Jim Mauro actually did not make a difference, I jumped to to wrong conclusion, based on an incorrect test setup. My sense is that interrupts are not being serviced. Assume that most cpu-s have been given a cli instruction, and just ignoring interrupts most of the time. Anyone has a suggestion on how to prove/disprove this? -- This message posted from opensolaris.org ___ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
Re: [dtrace-discuss] matching the -module-
interrupts not being serviced?
Do you mean device interrupts - NIC and HBA?
Or higher-level interrupts, like errors?
That seems a wee bit extreme, but intrstat should help
here. Or use dtrace and determine which interrupt services
routines are running. If you're referring to device interrupts,
the service routines all have intr in the function name.
j...@pae-g4-nv:~# dtrace -n 'fbt::*intr*:entry { @[probefunc] = count(); }'
dtrace: description 'fbt::*intr*:entry ' matched 339 probes
^C
The above probably seems extreme, but just run it for
a few seconds and see which probes actually fire. Fine
tune your probe spec from there.
On Apr 28, 2010, at 10:14 AM, Steve Gonczi wrote:
Do these post have some connection to the thread topic?
BTW. the mdb settings recommended by Jim Mauro actually did not make a
difference, I
jumped to to wrong conclusion, based on an incorrect test setup.
My sense is that interrupts are not being serviced. Assume that most cpu-s
have been given a cli instruction, and just ignoring interrupts most of the
time.
Anyone has a suggestion on how to prove/disprove this?
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
[dtrace-discuss] matching the -module-
Hello..
In the probe entry/return statements the - provider:module:function - is
used..
Say the module is libc, then.
provider:libc.so.1::entry
{
}
If i need to trace, function entry points in all other modules -but for-
libc, what is the easiest way ?
Thanks
Srihari
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Re: [dtrace-discuss] matching the -module-
Hi Srihari:
May be you can try something like
pid:::entry
/probemod!=libc.so.1/
{
}
-Angelo
On Apr 23, 2010, at 5:16 PM, Srihari Venkatesan wrote:
Hello..
In the probe entry/return statements the - provider:module:function - is
used..
Say the module is libc, then.
provider:libc.so.1::entry
{
}
If i need to trace, function entry points in all other modules -but for-
libc, what is the easiest way ?
Thanks
Srihari
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
