ddi_get_kt_did(9f) [sunos man page]

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

NAME

       ddi_get_kt_did - get identifier of current thread

SYNOPSIS

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

       kt_did_t ddi_get_kt_did(void);

INTERFACE LEVEL

       Solaris DDI specific (Solaris DDI)

DESCRIPTION

       The ddi_get_kt_did() function returns a unique 64-bit identifier for the currently running thread.

CONTEXT

       This routine can be called from user, kernel, or interrupt context. This routine cannot be called from a high-level interrupt context.

RETURN VALUES

       ddi_get_kt_did() always returns the identifier for the current thread. There are no error conditions.

SEE ALSO

       Writing Device Drivers

NOTES

       The value returned by this function can also be seen in adb or mdb as the did field displayed when using the thread macro.

       This interface is intended for tracing and debugging purposes.

SunOS 5.10							    15 May 2001 						ddi_get_kt_did(9F)

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

NAME

       ddi_can_receive_sig - Test for ability to receive signals

SYNOPSIS

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

       boolean_t ddi_can_receive_sig(void);

INTERFACE LEVEL

       Solaris DDI specific (Solaris DDI).

PARAMETERS

       None.

DESCRIPTION

       The  ddi_can_receive_sig() function returns a boolean value	indicating whether the current thread can receive signals sent by kill(2).
       If the return value is  B_FALSE, then the calling  thread  cannot receive  signals, and any  call  to  qwait_sig(9F),  cv_wait_sig(9F),	or
       cv_timedwait_sig(9F)  implicitly  becomes  qwait(9F),  cv_wait(9F), or  cv_timedwait(9F), respectively. Drivers that can block indefinitely
       awaiting an event should use this function to determine if additional means (such as timeout(9F)) may be necessary to avoid creating unkil-
       lable threads.

RETURN VALUES

       B_FALSE	   The	 calling  thread is in a state in which signals 	   cannot be  received. For  example, the thread is not associated
		   with a user process or is in the midst of exit(2) handling.

       B_TRUE	   The calling thread may receive a signal while blocked	    on a condition variable. Note  that  this  function  does  not
		   check to  determine whether signals are blocked (see sigprocmask(2)).

CONTEXT

       The ddi_can_receive_sig() function  may be called from user, kernel, or interrupt context.

SEE ALSO

       close(9E), cv_wait(9F), qwait(9F)

SunOS 5.11							    15 Dec 2003 					   ddi_can_receive_sig(9F)