Abstract: In at least some embodiments, a computer system comprises a processor, a memory coupled to the processor. The computer system also comprises a network interface coupled to the processor. The memory stores a firmware composition tool that, when executed by the processor, is to build a composite image comprising an arbitrary number of firmware update images according to a set of format rules that enables a self-describing aggregation of the arbitrary number of firmware update images.

Abstract: Techniques for management of target devices are provided. User input for management of a target device may be received. The user input may be converted into a first format. The first format may be encapsulated into a second format and sent over a communications channel. The second format may be un-encapsulated to recover the first format. The first format may be provided to the target devices.

Abstract: Techniques for management of target devices are provided. User input for management of a target device may be received. The user input may be converted into a first format. The first format may be encapsulated into a second format and sent over a communications channel. The second format may be un-encapsulated to recover the first format. The first format may be provided to the target devices.

Abstract: In at least some embodiments, a computer system comprises a processor, a memory coupled to the processor. The computer system also comprises a network interface coupled to the processor. The memory stores a firmware composition tool that, when executed by the processor, is to build a composite image comprising an arbitrary number of firmware update images according to a set of format rules that enables a self-describing aggregation of the arbitrary number of firmware update images.

Abstract: Non-disruptive disk ownership change in a distributed storage system is disclosed. The distributed storage system may having a first storage controller for managing a first storage pool, and a second storage controller. An exemplary method may include entering a preparation phase to transfer control of the first storage pool from the first storage controller to the second storage controller. The method may also include suspending writing normal I/O to the first storage pool and holding at the first storage controller any new I/O for the first storage pool. The method may also include rejecting the I/O requests held by the first storage controller after the second storage controller assumes ownership of the first storage pool.

Abstract: In one embodiment a computer system comprises a processor, a basic input/output system (BIOS) including logic instructions which, when executed by the processor, configure the processor to create a virtual AML device data structure, the data structure comprising a plurality of fields to hold arguments to a native firmware function, store at least one argument for the native firmware function in a register of the AML device data structure, store an entry point and a pointer value in a register of the virtual AML device data structure, and initiate an access request to a firmware access register in the AML device data structure.

Abstract: In one embodiment a computer system comprises a processor, a basic input/output system (BIOS) including logic instructions which, when executed by the processor, configure the processor to create a virtual AML device data structure, the data structure comprising a plurality of fields to hold arguments to a native firmware function, store at least one argument for the native firmware function in a register of the AML device data structure, store an entry point and a pointer value in a register of the virtual AML device data structure, and initiate an access request to a firmware access register in the AML device data structure.

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: 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: Embodiments of soft-partitioning systems and methods are disclosed. One system embodiment, among others, includes a first operating system (O.S.) instance and a second O.S. instance, a hardware component, a shared hardware proxy, and a shared hardware protocol interface configured with the shared hardware proxy to enable sharing of the hardware component between the first O.S. instance and the second O.S. instance.

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 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 system and method for implementing a fast reset of a computer system is described. In one implementation, the fast reset is implemented by adding a new ResetType to the EFIResetSystem( ) function. In particular, a third ResetType, i.e., “EfiResetFast” (FAST option), is added, which is passed as a parameter when calling the EFIResetSystem( ) function. In another implementation, the fast reset is implemented using a new EFI function, referred to herein as “EFIResetFast( )”. In either implementation, in response to a fast reset, the firmware skips several steps typically performed, including some of the core firmware construction, single cell initialization, memory testing, memory re-initialization, and partition creation, and proceeds directly to transfer of control of the platform to a software interface disposed between an OS and firmware.

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: A system and method for implementing a fast reset of a computer system is described. In one implementation, the fast reset is implemented by adding a new ResetType to the EFIResetSystem( ) function. In particular, a third ResetType, i.e., “EfiResetFast” (FAST option), is added, which is passed as a parameter when calling the EFIResetSystem( ) function. In another implementation, the fast reset is implemented using a new EFI function, referred to herein as “EFIResetFast( )”. In either implementation, in response to a fast reset, the firmware skips several steps typically performed, including some of the core firmware construction, single cell initialization, memory testing, memory re-initialization, and partition creation, and proceeds directly to transfer of control of the platform to a software interface disposed between an OS and firmware.