thread_wakeup(9r)thread_wakeup(9r)NAME
thread_wakeup - General: Wakes up all kernel threads waiting for the specified event
SYNOPSIS
void thread_wakeup(
vm_offset_t event );
ARGUMENTS
Specifies the event associated with the current kernel thread.
DESCRIPTION
The thread_wakeup routine wakes up all kernel threads waiting for the event specified in the event argument. This routine is actually a
convenience wrapper for the thread_wakeup_prim routine with the one_thread argument set to FALSE (wake up all kernel threads) and the
result argument set to THREAD_AWAKENED (wakeup is normal).
RETURN VALUES
None
SEE ALSO
Routines: assert_wait_mesg(9r), clear_wait(9r), thread_block(9r), thread_wakeup_one(9r)thread_wakeup(9r)
Check Out this Related Man Page
assert_wait_mesg(9r)assert_wait_mesg(9r)NAME
assert_wait_mesg - General: Asserts that the current kernel thread is about to block (sleep)
SYNOPSIS
void assert_wait_mesg(
vm_offset_t event,
boolean_t interruptible,
char *message );
ARGUMENTS
Specifies the event associated with the current kernel thread. Specifies a Boolean value that indicates how the kernel thread is awakened.
You can pass one of the following values: The current kernel thread is interruptible. This value means that a signal can awaken the current
kernel thread. The current kernel thread is not interruptible. This value means that only the specified event can awaken the current ker-
nel thread. Specifies a mnemonic for the type of wait. The ps command uses this mnemonic to print out more meaningful messages about a
process.
DESCRIPTION
The assert_wait_mesgroutine asserts that the current kernel thread is about to block (sleep) until the specified event occurs. This routine
sets a thread wait bit in the pointer to the thread structure associated with the current kernel thread. This bit signifies that this ker-
nel thread is on the appropriate wait hash queue, waiting for a wakeup call.
To actually block (put to sleep) the current kernel thread, call thread_block.
To issue a wakeup call on the specified event, call the thread_wakeup_prim or clear_wait routine.
CAUTIONS
You must not call assert_wait_mesg from a device driver's interrupt handler. The reason for this is that at interrupt context there is no
process to be put to sleep.
RETURN VALUES
None
SEE ALSO
Data Structures: thread(9s)
Routines: clear_wait(9r), current_thread(9r), thread_block(9r)
Reference Pages Section 1: ps
assert_wait_mesg(9r)
Hi Folks,
Today hasn't been the best one of my career in IT.
I've been a contractor for a major utility company for a number of years, on a number of seperate IT contracts mostly Unix. The company had 10 different flavours of unix and multiple different varsions of most of them.
At the... (3 Replies)