Processor Compatibility modes on IBM POWER9 based systems How To Summary The POWER9” based IBM Power Systems™ range offer a number of different Processor Compatibility modes. This document explains them. Objective Environment On a POWER9™ based, if we look at the Processor section of the Partition Profile we can see the compatibility modes which are available.ease Rivet) General | Processors | Memory | /0 | Virtual Adepters | Fower Controlling | Settings Detailed below are the current processing eettings for this partition prorie. Processing mode Obedicated @shared Processing units Total managed system processing units : 16.00 Minimum shared processing units os Desired shared processing units fo Maximum shared processing units fo Shared processor pool: Daa \vietwal processors Minimum processing units required for each virtual processor: 0.10 Newer operating system levels support 0.05 Minimum vitual processors © fig] Desired virtual processors: fg SY Maximum virtual processors : fg] [sharing mode Duncepped Weight : [735 Processor compatibility made: Gi || Sones! || ee | Brief explanation: POWER7 and POWERS modes limit the LPAR to the capabilities of that specific hardware, including number of SMT threads. If you want to carry out Live Partition Mobility (LPM) between a POWER and a POWER7 based server, the LPAR needs to be running in POWER7 mode. Similarly for POWERS the LPAR would need to be in POWERS (or POWER7) mode. Notice the two POWERS modes. In POWER9 mode, all the features of POWER are available, as introduced by Firmware version 940, If the LPAR is in POWER9_base mode, then some of the features will not be available. Only the features enabled in the Initial POWER9 Firmware (version 910) are available.Here are some notes from the Help page: Compatibility Mode This field displays the processor mode for this logical partition. A processor compatibility mode is a value assigned to a logical partition by the hypervisor that specifies the processor environment in which the logical partition can successfully operate. Also, processor compatibility modes enable you to move logical partitions between servers that have different processor types without upgrading the operating environments installed in the logical partitions. Depending on the capabilities of your managed system and the operating system of the logical partition, the processor compatibility mode can be one the following values: Default (default) This is the preferred processor compatibility mode that enables the hypervisor to determine the current mode for the logical partition. The current mode will be the most fully-featured mode supported by the operating system on the logical partition. You can specify default as the preferred processor compatibility mode. Also, if you do not specify a preferred mode, the system automatically sets the preferred mode to default, In most cases, this is the processor type of the server on which the logical partition is activated. For example, assume that the preferred mode is set to default and the logical partition is running on a POWER7 processor- based server. The operating environment supports the POWER7 processor capabilities so the hypervisor sets the current processor compatibility mode to POWER. POWER® Base The operating system version on the logical partition is set to use all the standard features of the POWER9 processor enabled by the firmware at level FW910. Logical partitions that use the POWER9_Base processor compatibility mode can run on POWER9 processor-based servers running firmware at level FW910, or later. POWERS The operating system version on the logical partition is set to use all the standard features of the POWERS processor. The logical partitions that use the POWER8 processor compatibility mode can run on POWERS processor-based servers. If the system's processor compatibility mode is lower than POWERS, the POWERS option is not available in the list. By using the Live Partition Mobility function, a logical partition with lower processor modes than POWERS can be migrated to the POWERS systems. POWER7 The operating system version on the logical partition is set to use all the standard features of the POWER7 processor. Logical partitions that use the POWER7 processor compatibility mode can run on POWER7 and POWERS processor-based servers. The POWER7 processor- based servers do not support the enhanced mode. The processor compatibility mode used by a logical partition depends on the following information: * The processor compatibility mode setting on the partition profile that you use to activate the logical partition* The processor compatibility modes that are supported by the operating system or system software that is installed on the logical partition ‘When you activate a logical partition, the managed system checks the processor compatibility mode setting on the partition profile, and determines whether the installed operating system or system software supports the specified mode. If so, the logical partition uses the processor compatibility mode from the partition profile. If not, the logical partition uses the most fully featured mode that is supported by the installed operating system or the system software. You cannot dynamically change the current processor compatibility mode of a logical partition. To change the current processor compatibility mode, you must change the preferred processor compatibility mode, shut down the logical partition, and restart the logical partition. The hypervisor then attempts to set the current processor compatibility mode to the preferred mode that you specified. If the operating environment installed in the logical partition does not support the preferred mode, the hypervisor can set the current mode to a lower mode than the preferred mode, but it cannot set the current mode to a higher mode than the preferred mode. For example, assume that a logical partition runs on a POWER9 processor-based server with firmware at level FW910 and you specify POWERS Base as the preferred mode. The operating environment installed in the logical partition does not support the POWER9 Base processor capabilities, but it does support the POWERS processor capabilities. When you activate the logical partition, the hypervisor assigns the POWERS processor compatibility mode as the current mode for the logical partition because the POWERS mode is the most fully featured mode that the operating environment supports and it is a lower mode than the preferred mode of POWERS Base. There is a KnowledgeCenter page here (https://www.ibm.com/support/knowledgecenter/9223-42H/p9hc3/p9hc3_pcmtypes.htm). Here are the new feature brought in with version 940 of the Firmware (https://delivery04.dhe.ibm.com/sar/CMA/SFA/08r8v/1/01VL940_041_027.html): New Features and Functions * User Mode NX Accelerator Enablement for PowerVM. This enables the access of NX accelerators such as the gzip engine through user mode interfaces. The IBM Virtual HMC (vHMC) 9.1.940 provides a user interface to this feature. The LPAR must be running in POWER9 compatibility mode to use this feature. For more information on compatibility modes, see the following two articles in the IBM Knowledge Center: 1) Processor compatibility mode overview (https://uww.ibm.com/support/knowledgecenter/POWER9/p9he3/p9he3_pcm.htm) 2) Processor compatibility mode definitions (https://www.ibm.com/support/knowledgecenter/POWER9/p9hc3/p9hc3_pcmdefs.htm) * Support for SR-IOV logical ports in I8M i restricted I/O mode.* Support for user mode enablement of the External Interrupt Virtualization Engine (KIVE). This user mode enables the management of interrupts to move from the hypervisor to the operating system for improved efficiency. Operating systems may also have to be updated to enable this support. The LPAR must be running in POWER9 compatibility mode to use this feature. For more information on compatibility modes, see the following two articles in the IBM Knowledge Center: 1) Processor compatibility mode overview (https://www.ibm.com/support/knowledgecenter/POWER9/p9he3/p9hc3_pcm.htm) 2) Processor compatibility mode definitions (https://www.ibm.com/support/knowledgecenter/POWER9/p9hc3/p9hc3_pcmdefs.htm) * Extended support for PowerVM Firmware Secure Boot. This feature restricts access to the Open Firmware prompt and validates all adapter boot driver code. Boot adapters, or adapters which may be used as boot adapters in the future, must be updated to the latest microcode from IBM Fix Central. The latest microcode will ensure the adapters support the Firmware Secure Boot feature of Power Systems, This requirement applies when updating system firmware from a level prior to FW940 to levels FW940 and later. The latest adapter microcode levels include signed boot driver code. If a boot-capable PCI adapter is not installed with the latest level of adapter microcode, the partition which owns the adapter will boot, but error logs with SRCs BAS400A5 or BAS4Q0A6 will be posted. Once the adapter(s) are updated, the error logs will no longer be posted. * Linux OS support was added for PowerVM LPARs for the PCle4 2x100GbE ConnectX-5 RoCE adapter with feature codes of #£C66/EC67 and CCIN 2CF3. Linux versions RHEL 7.5 and SLES 12.3 are supported Steps Please note: In order to make use of the NX (gzip) Accelerator, some additional, specific steps are needed. There is a blog about setting it up: Using the POWER9™ NX (gzip) accelerator in AIX (https://www.ibm.com/support/pages/node/6243342) Additional Information You can contact me: * Mailto:[email protected] * Twitter @powergaz (mips:/tittercom/power gaz)* LinkedIn https: //www.linkedin.com/in/gareth-coates-3b58a1144 (https: s/n linkedin.com/in/gareth-coates-365801144) My blog landing page is: Tricks of the Power Masters. A blog by Gareth Coates. (https://www.ibm.com/support/pages/node/1116939) Related Information Document Information More support for: 1BM Power Systems Software version: All Versions Operating system(s): AIX, BMC, HMC, IBM i, Linux Document number: 6243336 Modified date: 02 July 2020