Fault Diagnosis Driver Loading via Shared Memory Without Restart
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing fault diagnosis driver loading methods require system restarts, leading to inefficiencies and disruptions in business continuity, especially when in-band updating is unavailable due to network paralysis.
Innovation Solution
A method and apparatus for out-of-band fault diagnosis driver loading using a shared area mapped to system memory, involving a baseboard management controller to execute system control and management interrupts, enabling fault diagnosis driver loading without restarting the system, utilizing a standard format driver file and cyclic redundancy checks for data integrity, and employing intelligent platform management for status reporting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If fault diagnosis driver is updated using traditional in-band updating method, then driver can be updated, but system restart is required causing business interruption and downtime
Solution Approach 1:
The patent separates the driver update process into independent segments: the firmware volume file is stored in a shared area accessible by both the operating system and basic input output system, allowing the OS to load and update drivers without involving the BIOS layer, thus enabling updates without system restart
Solution Approach 2:
The patent introduces a shared memory area as an intermediary between the operating system and the basic input output system. This shared area allows the OS to directly access and update driver firmware without triggering a BIOS update that would require system restart, thereby maintaining system availability during driver updates
2Productivity
If fault diagnosis driver is updated without system restart, then business continuity is maintained, but data integrity and security become more challenging
Solution Approach 1:
The patent performs preliminary validation by computing and storing cyclic redundancy check (CRC) values for driver firmware in the shared area before actual loading. When the OS needs to update a driver, it first validates the firmware integrity using the pre-computed CRC value, ensuring data integrity before committing the update, thus maintaining both business continuity and reliability
Solution Approach 2:
The patent implements a feedback mechanism where the baseboard management controller continuously monitors and reports the status of the shared area and driver loading process to the operating system. This real-time feedback allows the system to detect and handle potential errors during driver updates without interrupting business operations, maintaining both productivity and data integrity
Data Source
AI summary
Embodiments of the present application provide a fault diagnosis driver loading method and apparatus, an electronic device, and a storage medium, and relate to the technical field of fault diagnosis driver loading. By adding a firmware volume file for a basic input and output system to a shared area through a client device, a system control interrupt is executed in a case that a computing device is powered on and the firmware volume file is detected, and the firmware volume file is acquired from the shared area; a power management and configuration interface command is executed to trigger a system management interrupt for the basic input and output system, and a fault diagnosis driver is loaded based on the firmware volume file.