[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-dtrace-discuss
Subject:    Re: [dtrace-discuss] matching the -module-
From:       Jim Mauro <james.mauro () oracle ! com>
Date:       2010-04-28 14:25:36
Message-ID: 2FA57D8F-4218-41B1-96F2-0B0C237D7272 () oracle ! com
[Download RAW message or body]

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.

jimm@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


[prev in list] [next in list] [prev in thread] [next in thread]