vparresources2.5 (2010 09)

v
vparresources2(5) vparresources2(5)
(For OA Based Partition Management Systems)
-a cpu::4
-a cpu:3/1/0/2
-a socket:3/2/0:cpu::2
you will have seven CPU-cores in your vPar configuration. With this configuration, you are only allowed
to delete four CPU-cores generically, using
-d cpu::4
You will get a command error if you specify a higher number.
Similarly, the two SLP CPU-cores can only be deleted via a SLP deletion
-d socket:3/2/0:cpu::2
To delete the CPU-core specified by resource path, you need to delete it by specifying the resource path
-d cpu:3/1/0/2
No matter how you choose to add and delete CPU-cores, the total must always remain between the min
and max specification for the vPar.
To help you manage these limitations, the
vparstatus command displays the count of CPU-cores in the
various categories when the
-v (detailed display) option is used. Here is the CPU-core portion of the
detailed display for the above configuration:
[CPU Details]
Min/Max: 0/16
User assigned [Path]: 3/1/0/2
Boot processor [Path]: 3/1/0/2
System assigned [Path]: 3/1/0/0
3/1/0/1
3/1/0/3
3/1/1/0
3/2/0/0
3/2/0/1
Non-socket-specific:
User assigned [Count]: 1
System assigned [Count]: 4
Socket-specific [Count]: Socket-ID/Count
3/2/0 2
Note that in the path displays, the user assigned CPU-core is also the boot processor, and so has been
shown in the Boot processor line.
The boot processor is meaningful only when a vPar is running. When a vPar is
DOWN, the Boot pro-
cessor line is empty.
The Boot Processor
The boot processor is the first processor to be activated when the vPar is booted, and is the one on which
all boot time activity takes place. It is assigned this responsibility by the system.
Multiple-Core CPU Sockets
Certain designs of CPUs are fabricated such that they share common low-level hardware. Each such
CPU is termed a core. The set of common hardware that they share is termed a socket. CPU-cores that
share a socket are called siblings. In a vPars environment, each CPU-core is managed as a separate
resource. So, it is possible to assign siblings to different virtual partitions. The system will attempt to
assign siblings to the same vPar whenever possible.
Further discussion of multiple-core CPU sockets is beyond the scope of this manpage. However, the
vparstatus -d command will display any sibling relationship that might exist.
CPU States
The platform support for CPU diagnostics includes CPU diagnostic tools running in the background.
Their purpose is to detect incipient errors in CPU hardware. As part of this operation, they manage
several co-existing CPU states:
OK, Indict, Deconf, Parent Indict, Parent Deconf. These
states are displayed by the vparstatus -d command. Detailed descriptions of these states are beyond
the scope of this manpage, but their effects on vPars configuration/operation are described next.
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3