Abstract: The present subject matter relates to an enclosure of a storage system. Each node of the enclosure comprises: at least two peer-to-peer connected class-A ESP devices to redundantly monitor and control a first set of environmental components shared within a respective node by the at least two class-A ESP devices; at least one class-B ESP device peer-to-peer connected to at least one class-B ESP device of another node in the enclosure to redundantly monitor and control a second set of environmental components shared between the respective node and the other node; and at least one class-X EM device peer-to-peer connected to the at least two class-A ESP devices and the at least one class-B ESP device of the respective node, and to a class-X EM device of the other node to redundantly supervise the monitoring and controlling of the first set and the second set of environmental components.

Abstract: Examples herein disclose detecting a modification to a first connection between components. In response to the detected modification, the examples provide a second connection redundant to the first connection. The second connection resumes a capability of the first connection.

Abstract: According to at least one embodiment, a method comprises partitioning a computer system into a plurality of soft partitions that each run an operating system. The method further comprises instantiating a separate firmware instance for each of the plurality of soft partitions, wherein each of the firmware instances provides a pre-defined firmware interface for the operating system of its respective soft partition.

Abstract: A system for sharing a device across a plurality of operating systems is provided. The system includes a sharable bit in the namespace for identifying whether the device is sharable. The system further includes one or more operating systems that are adapted to recognize the sharable bit.

Abstract: In one embodiment, a system, comprises a first computer system comprising at least a first diskless server, at least a first RAID controller coupled to the first diskless server, at least a first storage pool coupled to the RAID controller, and a remote management server coupled to the RAID controller via a an out-of-band communication link. The remote management server comprises a boot management module which, when executed, initiates a command to instruct the RAID controller to create at least a first logical volume in a memory module coupled to the RAID controller, transmits the command to the RAID controller via the out-of-band communication link, and transmits a boot image from the remote management server to the RAID controller via the out-of-band communication link. The RAID controller creates the first logical volume for the boot image in response to the command, and stores the boot image in the first logical volume.

Abstract: In one embodiment, a system, comprises a first computer system comprising at least a first diskless server, at least a first RAID controller coupled to the first diskless server, at least a first storage pool coupled to the RAID controller, and a remote management server coupled to the RAID controller via a an out-of-band communication link. The remote management server comprises a boot management module which, when executed, initiates a command to instruct the RAID controller to create at least a first logical volume in a memory module coupled to the RAID controller, transmits the command to the RAID controller via the out-of-band communication link, and transmits a boot image from the remote management server to the RAID controller via the out-of-band communication link. The RAID controller creates the first logical volume for the boot image in response to the command, and stores the boot image in the first logical volume.

Abstract: At least one simulated snapshot is created for a parent volume stored on a storage subsystem. A processor updates the at least one simulated snapshot in response to modification operations to the parent volume, wherein the at least one simulated snapshot stores metadata but not any prior version of data that is modified in response to the modification operations to the parent volume. The processor provides information relating to usage of the at least one simulated snapshot based on accessing the metadata of the at least one simulated snapshot.

Abstract: A system includes a plurality of partitions having respective operating systems, and a resource shared by the partitions. The resource has plural segments, where a first one of the segments is accessed to invoke a first interrupt. An operating system of a first one of the plurality of partitions invokes, in response to the first interrupt, a routine to cause generation of a second interrupt to a second one of the plurality of partitions.

Abstract: An ACPI-compatible system is provided that comprises a database for storing a device-specific descriptor for a hardware device. The system further comprises an ACPI agent operable to autonomously construct an ACPI table entry for the hardware device using the device-specific descriptor. Also, a method for an ACPI-compatible system autonomously constructing an ACPI table entry for a hardware device is provided. The method comprises receiving from firmware associated with the hardware device, a device-specific descriptor for such hardware device, and an ACPI agent executing on the ACPI-compatible system using the device-specific descriptor to autonomously construct an ACPI table entry for the hardware device.

Abstract: A method, memory system, and program product is described for providing extended functions in a digital device conforming to an intercompartment language specification. The method involves preparing a list of unused opcodes according to a version of the language of one compartment, and publishing the list of unused opcodes to code of a second compartment. Code of the second compartment then assigns opcodes to extended functions such that the opcodes assigned are unused opcodes in the version of language of both compartments. The assigned opcodes are used in generating code in the intercompartmental language, and published as a table of assigned opcodes with associated function names to the first compartment.

Abstract: A method for providing a firmware developer user interface in a multi-nodal computer system comprises polling for a break command during boot of a multi-nodal computer system and invoking a firmware developer user interface when the break command is encountered.

Abstract: Embodiments include writing a first data value to a validation variable through a fixed programming interface, where the validation variable includes multiple fields that correspond to multiple fields within a persistent variable. Contents of the validation variable are subsequently read through the fixed programming interface. When the validation variable contents include one or more differences from the first data value, one or more errors are identified.

Abstract: Methods and systems for developing firmware are provided. In certain embodiments, a method comprises defining a framework for firmware to be developed by firmware developers at different design centers. The method further comprises at least one of the firmware developers developing firmware as at least one component within the framework, and depositing the at least one component within a repository that is accessible from all of the design centers, wherein the repository includes contextual information about the at least one component deposited therein.

Abstract: A system comprises at least one processor, and supporting firmware for supporting at least one function of the at least one processor. The system further comprises logic operable to expand the functionality of the at least one function in a fashion that is not natively supported by the supporting firmware, and an interposer for supporting the expanded functionality of the at least one function. A method for expanding the functionality of an execution unit of a system comprises implementing an execution unit in a system, and implementing pre-existing support firmware for the execution unit in the system, wherein the pre-existing support firmware supports at least one function of the execution unit. The method further comprises implementing logic expanding the at least one function in a manner not supported by the pre-existing support firmware, and implementing an interposer to support the expansion of the at least one function.

Abstract: One embodiment of the invention is a method for changing control of a processor that is in an active state under the control of an operating system to a borrowed state wherein the processor is under control of firmware, comprising sending a request for a change in control to the operating system, deciding, by the operating system, whether to grant the request, placing the processor in a transitional state that is different from the active state, if the request is granted, and sending, by the operating system, an interrupt signal to move the processor from the transitional state into the borrowed state.

Abstract: Methods and systems for developing firmware are provided. In certain embodiments, a method comprises defining a framework for firmware to be developed by firmware developers at different design centers. The method further comprises at least one of the firmware developers developing firmware as at least one component within the framework, and depositing the at least one component within a repository that is accessible from all of the design centers, wherein the repository includes contextual information about the at least one component deposited therein.

Abstract: An ACPI-compatible system is provided that comprises a database for storing a device-specific descriptor for a hardware device. The system further comprises an ACPI agent operable to autonomously construct an ACPI table entry for the hardware device using the device-specific descriptor. Also, a method for an ACPI-compatible system autonomously constructing an ACPI table entry for a hardware device is provided. The method comprises receiving from firmware associated with the hardware device, a device-specific descriptor for such hardware device, and an ACPI agent executing on the ACPI-compatible system using the device-specific descriptor to autonomously construct an ACPI table entry for the hardware device.

Abstract: A method for remote access to a firmware developer user interface in a multi-nodal computer system comprises registering a manageability subsystem with a server; booting the multi-nodal computer system; entering, by a truant cell of the multi-nodal computer system, into a remote developer user interface mode; writing, by the truant cell, a remote developer user interface initialization sequence to shared memory of the manageability subsystem; acknowledging, by a processor of the manageability subsystem, acceptance of the initialization upon the registering; sending an open session request to the server; and spawning an interactive developer user interface terminal session on the server.

Abstract: A method for providing a firmware developer user interface in a multi-nodal computer system comprises polling for a break command during boot of a multi-nodal computer system and invoking a firmware developer user interface when the break command is encountered.

Abstract: A method for providing a firmware developer user interface in a multi-nodal computer system comprises invoking a firmware developer user interface during boot of a multi-nodal computer system, dumping a process state for the boot to a console, handing-off flow control of the boot to the developer user interface and accepting at least one command to firmware of the multi-nodal computer system via the console and the developer user interface.