Firmware Memory Migration Using CXL Pooled Memory During Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud computing systems lack a comprehensive computing logic and infrastructure to seamlessly update firmware for system memory without requiring server restarts, which is intrusive and disruptive, especially in environments where uninterrupted service is critical.
Innovation Solution
A firmware management system utilizing a firmware management engine that supports firmware management in cloud computing systems, employing hot-plugged memory (CXL pooled memory) and an orchestrator to migrate system memory data, update firmware, and manage virtual machines during the process without server restarts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware update is performed using conventional methods, then firmware can be updated, but server restart is required which disrupts service
Solution Approach 1:
The system segments memory into system memory and hot-plugged memory, allowing firmware updates to be performed on system memory while virtual machines continue to operate using hot-plugged memory. This segmentation enables non-disruptive firmware updates by isolating the update process from active workloads.
Solution Approach 2:
Hot-plugged memory acts as an intermediary, temporarily taking over the workload from system memory during firmware updates. The memory migration orchestrator coordinates the transfer of virtual machine memory from system memory to hot-plugged memory, enabling firmware updates without service disruption.
2Reliability
If memory training is performed to update firmware, then firmware can be updated, but the process is intrusive and requires system restart
Solution Approach 1:
The system performs preliminary actions by attaching hot-plugged memory and migrating virtual machine memory to it before initiating firmware updates. This preliminary setup allows the firmware update process to proceed without disrupting ongoing operations, as the hot-plugged memory is already prepared to take over the workload.
Solution Approach 2:
The system dynamically switches between system memory and hot-plugged memory during firmware updates. The memory migration orchestrator dynamically manages the transition, allowing the system to adapt its memory configuration in real-time to accommodate firmware updates without service disruption.
3Reliability
If server restart is performed for firmware update, then firmware can be updated, but virtual machines are disrupted
Solution Approach 1:
The system extracts the workload from system memory and transfers it to hot-plugged memory during firmware updates. This extraction allows the firmware update process to be performed on system memory without affecting the running virtual machines, which continue to operate using hot-plugged memory.
Solution Approach 2:
The system maintains continuity of useful action by ensuring that virtual machines continue to execute on hot-plugged memory during firmware updates. The memory migration orchestrator manages the transition seamlessly, allowing firmware updates to proceed while virtual machine operations continue uninterrupted.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
Methods, systems, and devices for providing firmware management using a firmware management engine of a cloud computing system are described. The firmware management engine supports using a hot-plugged memory (e.g., Compute Express Link (CXL) pooled memory) to temporarily migrate system memory (e.g., Central Processing Unit (CPU) local memory or CXL attached memory) of a server node, while performing firmware management operations (e.g., a firmware update) on the server node. The hot-plugged memory can be CXL pooled memory that is a shared at a rack level, the CXL pooled memory can be used to store system memory data of system memory while updating and activating new memory initialization firmware code. A virtual machine associated with the server node stays operational temporarily using the hot-plugged memory. Firmware management is performed on a server node while virtual machines associated with the server node and the system memory of the server node remain operational.