PSRADM(8) | Maintenance Commands and Procedures | PSRADM(8) |
psradm - change processor operational status
psradm -f | -i | -n | -s [-v] [-F] processor_id
psradm -a -f | -i | -n | -s [-v] [-F]
psradm -aS [-v]
The psradm utility changes the operational status of processors. The legal states for the processor are on-line, off-line, spare, faulted, no-intr, and disabled.
An on-line processor processes LWPs (lightweight processes) and can be interrupted by I/O devices in the system.
An off-line processor does not process any LWPs. Usually, an off-line processor is not interruptible by I/O devices in the system. On some processors or under certain conditions, it might not be possible to disable interrupts for an off-line processor. Thus, the actual effect of being off-line might vary from machine to machine.
A spare processor does not process any LWPs. A spare processor can be brought on-line, off-line or to no-intr by a privileged user of the system or by the kernel in response to changes in the system state.
A faulted processor is identified by the kernel, which monitors the behavior of processors over time. A privileged user can set the state of a faulted processor to be on-line, off-line, spare or no-intr, but must use the force option to do so.
A no-intr processor processes LWPs but is not interruptible by I/O devices.
With the -aS option, simultaneous multi-threading is disabled. The -a option means "apply to every core" and is currently required. Each CPU core has its SMT siblings placed in the disabled state, and they will effectively stay unused. That is, only one CPU in each core will be processing I/O, scheduling processes, etc. A CPU can only be moved back out of the disabled state with the -F option.
A processor can not be taken off-line, disabled, or made spare if there are LWPs that are bound to the processor unless the additional -F option is used. The -F option removes processor bindings of such LWPs before changing the processor's operational status. On some architectures, it might not be possible to take certain processors off-line or spare if, for example, the system depends on some resource provided by the processor.
At least one processor in the system must be able to process LWPs. At least one processor must also be able to be interrupted. Since an off-line or spare processor can be interruptible, it is possible to have an operational system with one processor no-intr and all other processors off-line or spare but with one or more accepting interrupts.
If any of the specified processors are powered off, psradm might power on one or more processors.
Only users with the PRIV_SYS_RES_CONFIG privilege can use the psradm utility.
The following options are supported:
-a
-f
-F
-i
-n
-S
-s
-v
The following operands are supported:
processor_id
Specify processor_id as an individual processor number (for example, 3), multiple processor numbers separated by spaces (for example, 1 2 3), or a range of processor numbers (for example, 1-4). It is also possible to combine ranges and (individual or multiple) processor_ids (for example, 1-3 5 7-8 9).
Example 1 Setting Processors to off-line
The following example sets processors 2 and 3 off-line:
% psradm -f 2 3
Example 2 Setting Processors to no-intr
The following example sets processors 1 and 2 no-intr:
% psradm -i 1 2
Example 3 Setting Processors to spare
The following example sets processors 1 and 2 spare, even if either of the processors was in the faulted state:
% psradm -F -s 1 2
Example 4 Setting All Processors on-line
% psradm -a -n
Example 5 Forcing Processors to off-line
The following example sets processors 1 and 2 offline, and revokes the processor bindings from the processes bound to them:
% psradm -F -f 1 2
The following exit values are returned:
0
>0
/etc/wtmpx
p_online(2), processor_bind(2), attributes(7), pbind(8), psrinfo(8), psrset(8)
psradm: processor 4: Invalid argument
psradm: processor 3: Device busy
psradm: processor 3: Device busy
psradm: processor 3: Device busy
psradm: processor 0: Not owner
psradm: processor 2: Operation not supported
April 25, 2019 | OmniOS |