kstat_intr(9s) [opensolaris man page]

kstat_intr(9S)						    Data Structures for Drivers 					    kstat_intr(9S)

NAME

       kstat_intr - structure for interrupt kstats

SYNOPSIS

       #include <sys/types.h>
       #include <sys/kstat.h>
       #include <sys/ddi.h>
       #include <sys/sunddi.h>

INTERFACE LEVEL

       Solaris DDI specific (Solaris DDI)

DESCRIPTION

       Interrupt statistics are kept in the kstat_intr structure. When kstat_create(9F) creates an interrupt kstat, the ks_data field is a pointer
       to one of these structures. The macro KSTAT_INTR_PTR() is provided to retrieve this field. It looks like this:

	 #define KSTAT_INTR_PTR(kptr)  ((kstat_intr_t *)(kptr)->ks_data)

       An interrupt is a hard interrupt (sourced from the hardware device itself), a soft interrupt (induced by the system through the use of some
       system interrupt source), a watchdog interrupt (induced by a periodic timer call), spurious (an interrupt entry point was entered but there
       was no interrupt to service), or multiple service (an interrupt was detected and serviced just prior to returning from  any  of	the  other
       types).

       Drivers	generally  report  only  claimed hard interrupts and soft interrupts from their handlers, but measurement of the spurious class of
       interrupts is useful for auto-vectored devices in order to pinpoint any interrupt latency problems in a particular system configuration.

       Devices that have more than one interrupt of the same type should use multiple structures.

STRUCTURE MEMBERS

	 ulong_t    intrs[KSTAT_NUM_INTRS];    /* interrupt counters */

       The only member exposed to drivers is the intrs member. This field is an array of counters. The driver must use the appropriate counter	in
       the array based on the type of interrupt condition.

       The following indexes are supported:

       KSTAT_INTR_HARD	       Hard interrupt

       KSTAT_INTR_SOFT	       Soft interrupt

       KSTAT_INTR_WATCHDOG     Watchdog interrupt

       KSTAT_INTR_SPURIOUS     Spurious interrupt

       KSTAT_INTR_MULTSVC      Multiple service interrupt

SEE ALSO

       kstat(9S)

       Writing Device Drivers

SunOS 5.11							    4 Apr 1994							    kstat_intr(9S)

ddi_intr_hilevel(9F)					   Kernel Functions for Drivers 				      ddi_intr_hilevel(9F)

NAME

       ddi_intr_hilevel - indicate interrupt handler type

SYNOPSIS

       #include <sys/ddi.h>
       #include <sys/sunddi.h>

       int ddi_intr_hilevel(dev_info_t *dip, uint_t inumber);

INTERFACE LEVEL

       Solaris	DDI specific (Solaris DDI). This interface is obsolete. Use the new interrupt interfaces referenced in Intro(9F). Refer to Writing
       Device Drivers for more information.

PARAMETERS

       dip	  Pointer to dev_info structure.

       inumber	  Interrupt number.

DESCRIPTION

       The ddi_intr_hilevel() function returns non-zero if the specified interrupt is a "high level" interrupt.

       High level interrupts must be handled without using system services that manipulate thread or process states, because these interrupts  are
       not blocked by the scheduler.

       In addition, high level interrupt handlers must take care to do a minimum of work because they are not preemptable.

       A  typical  high  level	interrupt handler would put data into a circular buffer and schedule a soft interrupt by calling ddi_trigger_soft-
       intr(). The circular buffer could be protected by using a mutex that was properly initialized for the interrupt handler.

       The ddi_intr_hilevel() function can be used before calling ddi_add_intr() to decide which type of interrupt handler should  be  used.  Most
       device  drivers	are  designed  with  the  knowledge  that the devices they support will always generate low level interrupts, however some
       devices, for example those using SBus or VME bus level 6 or 7 interrupts must use this test because on some machines those  interrupts  are
       high level (above the scheduler level) and on other machines they are not.

RETURN VALUES

       non-zero    indicates a high-level interrupt.

CONTEXT

       These functions can be called from useruser, interrupt, or kernel context.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Obsolete			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       ddi_add_intr(9F), Intro(9F), mutex(9F)

       Writing Device Drivers

SunOS 5.11							    16 Jan 2006 					      ddi_intr_hilevel(9F)