Persistent Memory Runtime Firmware Activation Without OS Restart
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Updating firmware in memory devices, particularly in persistent memory systems, often requires a system reboot, leading to interruptions in service and potential data loss, which is problematic for cloud service providers and end-user applications.
Innovation Solution
A runtime firmware activation (RFA) interface that allows new firmware to be activated during an operating system sleep state or soft reboot without shutting down the entire system, using an RFA interface that manages the process through BIOS and OS interactions, preserving virtual machine states and data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a system reboot is performed to activate new firmware for memory devices, then firmware updates can be applied, but service interruptions occur and storage services must be shut down
Solution Approach 1:
The system separates the firmware activation process from the operating system shutdown requirement. The memory device controller is divided into firmware region and operational region, allowing firmware to be updated independently while the OS and storage services continue running. This segmentation enables firmware updates without full system reboot.
Solution Approach 2:
The new firmware is loaded into a reserved firmware region in the memory device before the activation trigger occurs. This preliminary loading allows the firmware to be ready and validated before activation, ensuring that when the trigger is pulled, the switch to new firmware is immediate and seamless without requiring service shutdown.
2Reliability
If a system reboot is performed to activate new firmware, then firmware updates are applied, but downtime increases beyond acceptable service level agreements
Solution Approach 1:
The new firmware image is downloaded, validated for cryptographic signature, and loaded into the memory device's firmware region in advance. This preliminary preparation ensures that when activation is triggered, the switch occurs immediately without time-consuming firmware loading or validation during the activation moment itself.
Solution Approach 2:
The activation mechanism uses a trigger-based instant switch that skips the traditional reboot sequence. When the activation trigger is set, the system immediately transitions to the new firmware without going through OS shutdown, hardware initialization, and boot sequences, reducing downtime to minimal trigger propagation time.
3Reliability
If a system reboot is performed to activate new firmware, then firmware updates are applied, but storage services must be shut down and restarted
Solution Approach 1:
The memory device is segmented into operational memory regions and firmware storage regions. This allows the controller to maintain service operations in the operational regions while independently updating and activating firmware in the firmware region, enabling service continuity during firmware updates.
Solution Approach 2:
The firmware activation trigger acts as an intermediary mechanism between the firmware update process and service operations. By using this trigger-based activation, the system can switch firmware without involving the OS or storage services, allowing services to continue operating uninterrupted while the firmware transition occurs in the background.
4Reliability
If traditional firmware update methods are used requiring OS shutdown, then firmware can be updated, but data availability decreases
Solution Approach 1:
The new firmware is fully loaded, validated, and prepared in the memory device's firmware region before activation. This preliminary preparation ensures that when the activation trigger occurs, the new firmware is immediately available without any interruption to data access or service operations, maintaining continuous data availability.
Solution Approach 2:
The memory device controller performs self-updating by loading and activating new firmware internally without requiring OS involvement or service shutdown. The controller manages the firmware update process autonomously, allowing storage services to continue accessing data uninterrupted while the controller updates its own firmware.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
An interface is provided to update a firmware of a persistent memory module at runtime without restarting an operating system on the platform. The operating system initiates the firmware update by triggering a sleep state or by entering a soft reboot. The interface is capable of preserving the state of the platform for all memory modes that support volatile memory regions, persistent memory regions, or both, and reducing or eliminating the demand for access to memory during the firmware update. The persistent memory module is capable of updating the firmware responsive to a platform instruction generated using the interface, including preserving operational states for memory devices in all memory regions, including memory devices in volatile and persistent memory regions.