Abstract: Systems and methods are provided for a modular switch system that comprises disaggregated components, plugins, and managers that enable flexibility to adjust the dynamic configuration of a switch system. This can create modularity and customizability at different times of the lifecycle of the currently configured switch system.

Abstract: One embodiment can provide a node controller in a multiprocessor system. The node controller can include a processor interface to interface with a processor, a memory interface to interface with a fabric-attached memory, a node-controller interface to interface with a remote node controller, and a cache-coherence logic to operate in a first mode or a second mode. The cache-coherence logic manages cache coherence for a local memory of the processor coupled to the processor interface when operating in the first mode, and the cache-coherence logic manages cache coherence for the fabric-attached memory coupled to the memory interface when operating in the second mode.

Abstract: One embodiment can provide a node controller in a multiprocessor system. The node controller can include a processor interface to interface with a processor, a memory interface to interface with a fabric-attached memory, a node-controller interface to interface with a remote node controller, and a cache-coherence logic to operate in a first mode or a second mode. The cache-coherence logic manages cache coherence for a local memory of the processor coupled to the processor interface when operating in the first mode, and the cache-coherence logic manages cache coherence for the fabric-attached memory coupled to the memory interface when operating in the second mode.

Abstract: One embodiment can provide a node controller in a multiprocessor system. The node controller can include a processor interface to interface with a processor, a memory interface to interface with a fabric-attached memory, a node-controller interface to interface with a remote node controller, and a cache-coherence logic to operate in a first mode or a second mode. The cache-coherence logic manages cache coherence for a local memory of the processor coupled to the processor interface when operating in the first mode, and the cache-coherence logic manages cache coherence for the fabric-attached memory coupled to the memory interface when operating in the second mode.

Abstract: Examples relate to firmware-based provisioning of hardware resources. In some of the examples, firmware discovers and takes ownership of a hardware resource. At this stage, the firmware performs a test to verify the hardware resource. The firmware then assigns the hardware resource to an OS instance. At this stage, the firmware can suspend assigning further hardware resources to the OS instance in response to a satisfied notification from the OS instance.

Abstract: Examples disclosed herein relate to selecting and loading firmware volumes. A computing device is booted to a state where the computing device is capable of accessing a memory available to multiple other computing devices. The memory includes multiple firmware volumes. In one example, at least one firmware volume is selected based on a hardware configuration or hardware components of the computing device. The selected firmware volumes are loaded.

Abstract: Examples relate to firmware-based provisioning of hardware resources. In some of the examples, firmware discovers and takes ownership of a hardware resource. At this stage, the firmware performs a test to verify the hardware resource. The firmware then assigns the hardware resource to an OS instance. At this stage, the firmware can suspend assigning further hardware resources to the OS instance in response to a satisfied notification from the OS instance.

Abstract: Examples disclosed herein relate to an error coordination message for a blade device having a logical processor in another system firmware (SFW) domain. Examples include a partition of a blade system to run an operating system (OS) utilizing blade devices including respective logical processors operating in different SFW domains. Examples further include an error coordination message made available to one of the blade devices by another of the blade devices.

Abstract: A dynamic firmware update process includes finding an updated version of a dynamic data-object in firmware memory. A callback handle for an in-use version of the dynamic data object in use by a consumer is identified. The consumer of updated version of dynamic data object is notified using the callback handle.

Abstract: Examples disclosed herein relate to selecting and loading firmware volumes. A computing device is booted to a state where the computing device is capable of accessing a memory available to multiple other computing devices. The memory includes multiple firmware volumes. In one example, at least one firmware volume is selected based on a hardware configuration or hardware components of the computing device. The selected firmware volumes are loaded.

Abstract: Examples relate to firmware-based provisioning of hardware resources. In some of the examples, firmware discovers and takes ownership of a hardware resource. At this stage, the firmware performs a test to verify the hardware resource. The firmware then assigns the hardware resource to an OS instance. At this stage, the firmware can suspend assigning further hardware resources to the OS instance in response to a satisfied notification from the OS instance.

Abstract: Examples disclosed herein relate to making memory of compute and expansion blade devices available for use by an operating system (OS). Examples include making available, for use by an OS, a compute logical processor of the compute blade device, identified memory of the compute blade device, and identified memory of an expansion blade device. Examples further include making the expansion logical processor unavailable to the OS.

Abstract: Examples relate to firmware-based provisioning of hardware resources. In some of the examples, firmware discovers and takes ownership of a hardware resource. At this stage, the firmware performs a test to verify the hardware resource. The firmware then assigns the hardware resource to an OS instance. At this stage, the firmware can suspend assigning further hardware resources to the OS instance in response to a satisfied notification from the OS instance.

Abstract: Examples disclosed herein relate to identifying memory of a blade device for use by an operating system (OS) of a partition including the blade device. Examples include identifying memory of a first blade device associated with a first logical processor of the first blade device for use by an OS of a partition including the first blade device and a second blade device, wherein the OS is executed by at least a second logical processor of the second blade device.

Abstract: Hiding logical processors from an operating system (OS) of a computer is described. In an example, a method of hiding at least one logical processor in a computer having a plurality of logical processors includes: initializing the plurality of logical processors by executing a pre-boot routine in system firmware; identifying at least one logical processor of the plurality of logical processors to be hidden from an operating system (OS) of the computer to provide at least one hidden logical processor and at least one visible logical processor; placing each of the at least one hidden logical processor into a system management mode (SMM) by executing a park routine in the system firmware; and booting the OS of the computer to use the at least one visible logical processor.

Abstract: Examples disclosed herein relate to updating a commit list to indicate data to be written to a firmware interface (FI) variable repository. Examples include storing target data in a variable repository cache of system management memory of a computing device during a given SMM event, updating a commit list, during the given SMM event, to indicate that the target data is to be written to the FI variable repository, and ending the given SMM event without at least some portion of the target data being written to the FI variable repository during the given SMM event.

Abstract: Examples disclosed herein relate to an error coordination message for a blade device having a logical processor in another system firmware (SFW) domain. Examples include a partition of a blade system to run an operating system (OS) utilizing blade devices including respective logical processors operating in different SFW domains. Examples further include an error coordination message made available to one of the blade devices by another of the blade devices.

Abstract: Examples disclosed herein relate to identifying memory of a blade device for use by an operating system (OS) of a partition including the blade device. Examples include identifying memory of a first blade device associated with a first logical processor of the first blade device for use by an OS of a partition including the first blade device and a second blade device, wherein the OS is executed by at least a second logical processor of the second blade device.

Abstract: Examples disclosed herein relate to making memory of compute and expansion blade devices available for use by an operating system (OS). Examples include making available, for use by an OS, a compute logical processor of the compute blade device, identified memory of the compute blade device, and identified memory of an expansion blade device. Examples further include making the expansion logical processor unavailable to the OS.

Abstract: Examples disclosed herein relate to updating a commit list to indicate data to be written to a firmware interface (FI) variable repository. Examples include storing target data in a variable repository cache of system management memory of a computing device during a given SMM event, updating a commit list, during the given SMM event, to indicate that the target data is to be written to the FI variable repository, and ending the given SMM event without at least some portion of the target data being written to the FI variable repository during the given SMM event.