Browse Prior Art Database

Methods Of Intercommunication Among Common Service Processor, Hardware System Console, And Firmware Partition Manager For Logical Partition Management, Instantiation, And Termination

IP.com Disclosure Number: IPCOM000014006D
Original Publication Date: 2001-Apr-20
Included in the Prior Art Database: 2003-Jun-19
Document File: 3 page(s) / 47K

Publishing Venue

IBM

Abstract

Methods Of Intercommunication Among Common Service Processor, Hardware System Console, And Firmware Partition Manager For Logical Partition Management, Instantiation, And Termination Disclosed is the methods used by Common Service Processor (CSP), Hardware System Console (HSC), and System Firmware Partition Manager (PM) for the management, instantiation, and termination of logical partitions in a logical partitioned (LPAR) system.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Methods Of Intercommunication Among Common Service Processor, Hardware

System Console, And Firmware Partition Manager For Logical Partition

Management, Instantiation, And Termination

Disclosed is the methods used by Common Service Processor (CSP), Hardware System Console (HSC), and System Firmware Partition Manager (PM) for the management, instantiation, and termination of logical partitions in a logical partitioned (LPAR) system.

In the logically partitionable system, the HSC is responsible to manage the assignments of system resources to all available logical partitions supported by the system. These assignments are saved in several tables in NVRAM of the system. The CSP provides a communication link whereby the HSC can access NVRAM to maintain and update these tables. On the other hand, the PM acts upon requests from the HSC to instantiate logical partitions by satisfying and allocating partitions' resources assigned and indicated in these tables. The PM also reclaims resources and cleans up the partitions when they terminate and cease to run. As a result of the instantiations and terminations of partitions, the PM will directly update these same tables in NVRAM for the information related to partition state-status, processor state, etc..

Because of multiple writers to these tables, it is mandatory that these tables must be updated timely and correctly. Once the data structures of the tables are defined, the disclosed methods require that the designer of these tables to clearly identify the ownership of every field of the tables. The owner of a field can write to the field. However, all parties can read any field of the tables. Since some fields are used by the HSC and the PM at different times to perform the acknowledgment dialog, the ownership may be switched based on content of the fields.

For the discussion, the entries of the processor table, I/O slot table, and partition table are shown below in their C code structures.

Note that the owner (has write access to the field) is listed after the field description.

Only a couple of fields can be written by multiple writers and that is shown as OWNER1/OWNER2 (i.e. HSC/PM).

typedef struct {

char lpar_id; /* Logical Partition ID. HSC */

char status; /* Processor Status. CSP */

char state; /* Processor State. PM */

char proc_pir; /* Processor PIR number. CSP */

char phys_loc[32]; /* Physical Location Code. CSP */

char lpar_reset_vector; /* Hypervisior reset vector. CSP */

char unused[2]; /* Reserved. CSP */

1

Page 2 of 3

} LPAR_PROC;

typedef struct {

char lpar_id; /* Logical Partition ID. HSC */

char status; /* Slot status. CSP */

char state; /* Slot state. PM */

char phb_num; /* PHB number. PM */

char dev_id[4]; /* Device Id. PM */

char slot_phys_loc[7]; /* Physical Location Code. PM */

char slot_num; /* Slot number. PM */

char PCI_class[3]; /* PCI class code. PM */

char flag3; /* Reserved. CSP */ } LPAR_IO_SLOT;

typedef struct {

char lpar_id; /* Logical Partition ID. HSC */

char...