Hybrid BIOS-OS Error Handling Without SMI/SMM Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional firmware-first and operating-system-first error handling models in information handling systems face issues such as security vulnerabilities and performance degradation due to System Management Interrupts (SMIs) and System Management Mode (SMM), and they fail to provide error reporting to computing device management systems that do not manage the operating system.
Innovation Solution
A hybrid firmware-first/operating-system-first error handling system that initiates BIOS firmware operations during initialization, disables firmware handling if the operating system is capable, and instructs the operating system to perform error handling during runtime, using a shared memory subsystem to store error information accessible by both BIOS and operating system, thereby eliminating SMI/SMM operations and enabling error reporting to management systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware-first error handling using SMI/SMM is implemented, then error detection and logging capability is improved, but security vulnerabilities and performance degradation occur due to SMI/SMM latency
Solution Approach 1:
The patent segments error handling into two distinct phases: firmware-first error handling during initialization process and operating-system-first error handling during runtime. This segmentation allows each phase to use the most appropriate error handling approach for its specific requirements, eliminating the need for SMI/SMM during runtime while maintaining comprehensive error detection capability.
Solution Approach 2:
The patent implements dynamic switching between firmware-first and operating-system-first error handling models based on the system state. During initialization, firmware-first handling is active; after the operating system is loaded and configured, the system dynamically transitions to operating-system-first handling. This dynamic approach optimizes both security/performance and error detection capability.
2Object-affected harmful factors
If operating-system-first error handling model is used, then security and performance are improved by eliminating SMI/SMM operations, but error reporting to computing device management systems is lost
Solution Approach 1:
The patent performs preliminary action by configuring the operating system during initialization to use an error reporting interface that can communicate with both the operating system and the computing device management system. This preliminary configuration ensures that error reporting capability is established before the transition to operating-system-first handling, preventing information loss.
Solution Approach 2:
The patent introduces an intermediary error reporting interface that bridges the operating system and the computing device management system. This intermediary allows errors detected during runtime to be reported to management systems without requiring SMI/SMM operations, thus maintaining security and performance while preserving error reporting capability.
3Reliability
If firmware-first error handling is used during initialization, then error detection capability is ensured, but system latency increases due to SMI/SMM operations
Solution Approach 1:
The patent segments the system operation into initialization phase and runtime phase, applying different error handling strategies to each. During initialization, firmware-first handling ensures comprehensive error detection. During runtime, operating-system-first handling eliminates SMI/SMM latency. This segmentation resolves the contradiction by applying the appropriate approach to each phase.
Solution Approach 2:
The patent implements periodic action by switching error handling modes at specific points in the system lifecycle. Firmware-first handling is active during the initialization period, then the system periodically transitions to operating-system-first handling for the runtime period. This periodic switching optimizes error detection during initialization while minimizing latency during runtime.
Data Source
AI summary
A hybrid firmware-first/operating-system-first error handling system includes a Basic Input/Output System (BIOS) subsystem coupled to a processing system. The BIOS subsystem begins an initialization process for a computing device and, in response, configures the processing system to perform processing system firmware-first error handling operations and, for any errors that are detected during at least a portion of the initialization process, performs BIOS firmware-first error handling operations. During the initialization process, the BIOS subsystem determines that an operating system provided by the processing system is configured to perform error handling and, in response, disables the performance of processing system firmware-first error handling operations by the processing system, and instructs the operating system to perform operating-system-first error handling operations such that the operating system performs the operating-system-first error handling operations for any errors that are detected during runtime of the computing device.