svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
swi(9)
These functions are used to register and schedule software inter‐
rupt handlers. Software interrupt handlers are attached to a
software interrupt thread, just as hardware interrupt handlers
are attached to a hardware interrupt thread. Multiple handlers
can be attached to the same thread. Software interrupt handlers
can be used to queue up less critical processing inside of hard‐
ware interrupt handlers so that the work can be done at a later
time. Software interrupt threads are different from other kernel
threads in that they are treated as an interrupt thread. This
means that time spent executing these threads is counted as in‐
terrupt time, and that they can be run via a lightweight context
switch. The function is used to add a new software interrupt
handler to a specified interrupt event. The argument is an op‐
tional pointer to a pointer. If this argument points to an ex‐
isting event that holds a list of interrupt handlers, then this
handler will be attached to that event. Otherwise a new event
will be created, and if is not then the pointer at that address
to will be modified to point to the newly created event. The ar‐
gument is used to associate a name with a specific handler. This
name is appended to the name of the software interrupt thread
that this handler is attached to. The argument is the function
that will be executed when the handler is scheduled to run. The
parameter will be passed in as the only parameter to when the
function is executed. The value specifies the priority of this
interrupt handler relative to other software interrupt handlers.
If an interrupt event is created, then this value is used as the
vector, and the argument is used to specify the attributes of a
handler such as The argument points to a cookie. This cookie
will be set to a value that uniquely identifies this handler, and
is used to schedule the handler for execution later on. The
function is used to teardown an interrupt handler pointed to by
the argument. It detaches the interrupt handler from the associ‐
ated interrupt event and frees its memory. The function is used
to schedule an interrupt handler and its associated thread to
run. The argument specifies which software interrupt handler
should be scheduled to run. The argument specifies how and when
the handler should be run and is a mask of one or more of the
following flags: Specifies that the kernel should mark the speci‐
fied handler as needing to run, but the kernel should not sched‐
ule the software interrupt thread to run. Instead, will be exe‐
cuted the next time that the software interrupt thread runs after
being scheduled by another event. Attaching a handler to the
clock software interrupt thread and using this flag when schedul‐
ing a software interrupt handler can be used to implement the
functionality performed by in earlier versions of The and vari‐
ables contain pointers to the software interrupt handlers for the
tty and clock software interrupts, respectively. is used to hang
tty software interrupt handlers off of the same thread. is used
to hang delayed handlers off of the clock software interrupt
thread so that the functionality of can be obtained in conjunc‐
tion with The handler cookie is used to schedule software inter‐
rupt threads to run for the VM subsystem. The and functions re‐
turn zero on success and non-zero on failure. The function will
fail if: The system-imposed limit on the total number of
processes under execution would be exceeded. The limit is given
by the MIB variable The argument specifies The argument points to
a hardware interrupt thread. Either of the or arguments are The
flag is specified and the interrupt event pointed to by already
has at least one handler, or the interrupt event already has an
exclusive handler. The function will fail if: A software inter‐
rupt handler pointed to by is The and functions first appeared in
They replaced the function which appeared in and the and func‐
tions which date back to at least The function first appeared in
Most of the global variables described in this manual page should
not be global, or at the very least should not be declared in