OS-Firmware Adapter Error Notification via SCLP
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computing environments, adapter errors often go undetected by processor firmware since they are reported directly to the operating system, leading to unaddressed hardware issues as there is no existing methodology for the operating system to request repair actions from firmware.
Innovation Solution
A computer program product facilitates communication between the operating system and firmware by using a Service Call Logical Processor (SCLP) instruction to notify the firmware of adapter errors and initiate actions such as resetting or requesting repairs, enabling coherent system-wide recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If adapter errors are reported directly to the operating system, then the operating system can detect errors quickly, but the firmware cannot address these errors leading to unaddressed hardware issues
Solution Approach 1:
The patent introduces an intermediary mechanism (hypercall interface and control block) that enables communication between the operating system and firmware. When the OS detects an adapter error, it uses a hypercall to notify the firmware, which then processes the error through its established error handling routines. This intermediary approach allows both the OS (which detects errors quickly) and firmware (which can address hardware errors) to participate in the error handling process, resolving the contradiction between fast detection and proper addressing.
2Ease of operation
If device drivers handle adapter errors independently, then specific adapter issues can be addressed, but system-wide coherent recovery cannot be achieved
Solution Approach 1:
The patent merges the error handling responsibilities of device drivers and firmware into a unified system-wide process. The OS notifies the firmware through a hypercall, and the firmware processes errors using standardized routines that can handle multiple adapter types consistently. This merging eliminates fragmented error handling while preserving the ability to address specific adapter issues, achieving both ease of operation and system-wide recovery consistency.
3Reliability
If firmware handles all hardware errors, then consistent error handling is achieved, but operating system awareness and coordination are lost
Solution Approach 1:
The patent implements preliminary action by having the operating system detect and identify adapter errors first, then immediately notify the firmware through a hypercall. This allows the OS to prepare error information and initiate the notification process before the firmware begins its error handling routine. The preliminary detection and notification by the OS reduces delays while the firmware maintains consistent handling through its standardized processing approach.
Data Source
Figure 1
Figure 2A
Figure 2B~3
AI summary
Notification of hardware actions to be taken responsive to hardware events is facilitated. An operating system coupled, but external to, the hardware notifies firmware of the hardware action to be taken.