Abstract:
A resource and partition manager includes a power on/power off mechanism that is used to assure a hardware resource is powered down when control of the resource is removed from a logical partition, and to assure the hardware resource is powered up when control of the hardware resource is transferred to a logical partition. In the alternative, the resource and partition manager may simply place the hardware resource in a power on reset state when the hardware resource is transferred to a logical partition. In this manner, when made available to a partition, the hardware resource is in a power-on reset state, which is the state typically expected by the logical partition.
Abstract:
A resource and partition manager of the preferred embodiments includes a lock mechanism that operates on a plurality of locks that control access to individual hardware resources. The resource and partition manager uses the lock mechanism to obtain a lock on a hardware resource when transferring control of the hardware resource to a logical partition that is powering on and when removing the hardware resource from a logical partition that is powering off. The resource and partition manager uses the lock mechanism to remove control of a hardware resource from, or return control to, an operating logical partition in order to facilitate hardware service operations on that hardware resource or on the physical enclosure in which it is contained. The preferred embodiments also include methods for releasing system resources and address bindings allocated to a hardware resource when control the hardware resource is removed from a logical partition.
Abstract:
PROBLEM TO BE SOLVED: To enable automatic recovery from errors in an I/O fabric. SOLUTION: A device, program products, and a method propagate errors detected in I/O fabric elements within a I/O fabric used for combining one or more end point I/O resource(s) with a processing unit in a computer. More specifically, errors are propagated to an end point I/O resource which is affected by the I/O fabric related to a recovery from the errors in the I/O fabric. Then a device driver or other program codes, used for accessing to each affected I/O resource, can be recovered asynchronously from the errors propagated from the accompanied I/O resources. In this way, recovery from the errors in the I/O fabric elements can often be made, before waiting for all the affected I/O resources to finish recovery. Also, the I/O fabric can be composed dynamically so as to be available for both recoverable end point resources and to unrecoverable endpoint I/O resources. In concrete terms, the I/O fabric element in the I/O fabric can be composed dynamically so that it enables machine check notification in the I/O fabric element, when it detects that the end point I/O resource has essentially become unrecoverable. COPYRIGHT: (C)2005,JPO&NCIPI
Abstract:
PROBLEM TO BE SOLVED: To enable optimum processes for a compartment managing operation such as a state changing operation for a variety of situations by providing a logically compartmentalized computer, a program recording medium, and a method using a flexible and adaptable communications interface between each compartment and a compartment manager. SOLUTION: With a request for executing the compartment managing operation, a compartment function indicating whether or not an asynchronous report should be generated or suppressed in relation to the execution of the compartment managing operation by a compartment manager is supported. As a result, the asynchronous report is selectively generated in relation to the execution of the compartment managing operation based on an instruction included in the request achieved by the compartment about such an operation. COPYRIGHT: (C)2005,JPO&NCIPI
Abstract:
PROBLEM TO BE SOLVED: To provide a computer system including a plurality of physical storage devices, wherein a storage device has a nonvolatile memory including bus numbering information of busses of the storage device itself and busses of one or more adjacent storage devices. SOLUTION: In a preferred implementation, all physical storage devices are provided with non-volatile memories including bus numbering information for their own busses and busses of both adjacent storage devices. This creates a distributed database of the interconnection topology for the computer system. Because storage devices contains bus numbering information about storage devices adjacent to them, bus numbers for busses in physical storage devices are made persistent across numerous different system reconfigurations. A preferred embodiment includes a bus number manager which reads the nonvolatile memories in the physical storage devices during initial program load (i.e., boot) and reconstructs the interconnection topology on the basis of information read from the nonvolatile memories and assigns bus numbers to busses in accordance with a derived interconnection topology. COPYRIGHT: (C)2006,JPO&NCIPI
Abstract:
A resource and partition manager of the preferred embodiments includes a lock mechanism that operates on a plurality of locks that control access to individual I/O slots. The resource and partition manager uses the lock mechanism to obtain a lock on an I/O slot when transferring control of the I/O slot to a logical partition that is powering on and when removing the I/O slot from a logical partition that is powering off. The resource and partition manager uses the lock mechanism to remove control of an I/O slot from, or return control to, an operating logical partition in order to facilitate hardware service operations on that I/O slot or on the physical enclosure in which it is contained.
Abstract:
A resource and partition manager includes a power on/power off mechanism that is used to assure a hardware resource is powered down when control of the resource is removed from a logical partition, and to assure the hardware resource is powered up when control of the hardware resource is transferred to a logical partition. In the alternative, the resource and partition manager may simply place the hardware resource in a power on reset state when the hardware resource is transferred to a logical partition. In this manner, when made available to a partition, the hardware resource is in a power-on reset state, which is the state typically expected by the logical partition.
Abstract:
A resource and partition manager includes a power on/power off mechanism that is used to assure a hardware resource is powered down when control of the resource is removed from a logical partition, and to assure the hardware resource is powered up when control of the hardware resource is transferred to a logical partition. In the alternative, the resource and partition manager may simply place the hardware resource in a power on reset state when the hardware resource is transferred to a logical partition. In this manner, when made available to a partition, the hardware resource is in a power-on reset state, which is the state typically expected by the logical partition.
Abstract:
A resource and partition manager of the preferred embodiments includes a lock mechanism that operates on a plurality of locks that control access to individual hardware resources. The resource and partition manager uses the lock mechanism to obtain a lock on a hardware resource when transferring control of the hardware resource to a logical partition that is powering on and when removing the hardware resource from a logical partition that is powering off. The resource and partition manager uses the lock mechanism to remove control of a hardware resource from, or return control to, an operating logical partition in order to facilitate hardware service operations on that hardware resource or on the physical enclosure in which it is contained. The preferred embodiments also include methods for releasing system resources and address bindings allocated to a hardware resource when control the hardware resource is removed from a logical partition.
Abstract:
A resource and partition manager of the preferred embodiments includes a lock mechanism that operates on a plurality of locks that control access to individual I/O slots. The resource and partition manager uses the lock mechanism to obtain a lock on an I/O slot when transferring control of the I/O slot to a logical partition that is powering on and when removing the I/O slot from a logical partition that is powering off. The resource and partition manager uses the lock mechanism to remove control of an I/O slot from, or return control to, an operating logical partition in order to facilitate hardware service operations on that I/O slot or on the physical enclosure in which it is contained.