Boot Load Firmware for Time-Coordinated Computing Tuning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information handling systems face challenges in managing firmware updates for performance-tuned systems, particularly in maintaining high performance while avoiding negative impacts on latency and power consumption, especially when using Time Coordinated Computing (TCC) features.
Innovation Solution
A thin boot load firmware map is used to dynamically create a runtime TCC map for tuning TCC attributes in board support packages, I/O, and processor fabric, allowing for reapplication of TCC attributes without additional reboots, using a best known configuration-based firmware update process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If TCC features are implemented for real-time tuning, then compute performance is improved, but latency and other performance characteristics may deteriorate if not carefully managed
Solution Approach 1:
The patent implements dynamic TCC attribute tuning that can be adjusted at runtime without requiring system reboots. The boot loader dynamically creates runtime TCC maps based on current system state and applies updates to hardware components like CAT, GT COS, and IOMMU, enabling adaptive performance optimization that responds to changing workload conditions while maintaining latency guarantees.
Solution Approach 2:
The patent performs preliminary actions by pre-configuring TCC attributes in the boot loader before the operating system loads. The boot loader retrieves current TCC attribute values, applies default or updated values, and creates a runtime TCC map in advance, ensuring that real-time tuning capabilities are ready before the system enters operation mode.
2Productivity
If firmware updates are applied to tune TCC attributes, then performance tuning is improved, but system stability may be affected if additional reboots are required
Solution Approach 1:
The boot loader performs preliminary retrieval and application of TCC attribute values before the operating system loads. By pre-processing firmware updates and creating runtime TCC maps in advance, the system avoids the need for additional reboots during operation, maintaining system stability while enabling effective performance tuning.
Solution Approach 2:
The boot loader acts as an intermediary between firmware updates and the operating system. It retrieves current TCC attributes, applies updates, and creates a runtime map that the OS can consume without requiring a reboot. This intermediary approach decouples the firmware update process from system restart requirements, ensuring stability.
3Ease of operation
If a thin boot load firmware map is used to dynamically create runtime TCC map, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The patent segments the firmware management process into distinct phases: boot loader retrieves current TCC attributes, applies updates, and creates a runtime TCC map. This segmentation separates concerns between the boot loader and operating system, simplifying the update process while managing complexity through modular architecture.
Solution Approach 2:
The boot loader creates a copy of the TCC attribute map at runtime based on current system state. This runtime TCC map is a dynamic copy that reflects the actual hardware configuration, allowing the system to operate with a simplified view of complexity while maintaining full functionality.
4Productivity
If TCC attributes are re-applied without additional reboot, then productivity is improved, but loss of time may increase due to complex runtime tuning processes
Solution Approach 1:
The boot loader performs all necessary TCC attribute retrieval, validation, and map creation actions before the operating system loads. By completing these preliminary actions during the boot phase rather than at runtime, the system avoids time-consuming operations during operation while still achieving update efficiency.
Data Source
AI summary
A disclosed method retrieves a first set of time coordinated computing (TCC) attributes from firmware objects of an existing boot image and a second group of TCC attributes from firmware objects of an update boot image, such as a BKC firmware update. A runtime TCC attributes map is generated based on the first and second TCC attributes. Device-specific, TCC firmware objects are created for one or more devices based on the runtime TCC attributes map, and attributes of the one or more devices are tuned at OS runtime based on the device-specific time coordinated firmware objects. Disclosed teaching achieves silicon-agnostic seamless BKC firmware updates without compromising on platform performance against TCC attributes. At OS runtime, dynamic tuning to time TCC attributes for various system software modules which have a hard dependency on hardware/firmware can be achieved without a platform reboot.