OEM Memory Allocation Module for Dynamic Boot Stage Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current information handling systems are limited in their ability to dynamically allocate and reallocate memory during the pre-boot, boot, and runtime stages, leading to inefficiencies and wasted memory resources.
Innovation Solution
The implementation of an OEM-defined chipset agnostic memory allocation module that allows for dynamic memory allocation and reallocation through the creation of a virtual interface, enabling the redefinition of memory maps and the reuse of reserved memory spaces across different stages of the boot process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If memory is allocated for pre-boot and boot stages, then system initialization can proceed, but memory resources are wasted during runtime when these stages are no longer needed
Solution Approach 1:
The patent implements dynamic memory allocation by creating a virtual interface that allows the memory map to be redefined at runtime. The system can dynamically adjust memory allocations between pre-boot/boot stages and runtime stages, transitioning from static reserved memory to flexible dynamic allocation based on actual operational needs.
Solution Approach 2:
The patent changes the memory allocation parameters by introducing a virtual interface layer between the physical memory and the boot stages. This virtual interface enables the system to modify memory mapping parameters at runtime, allowing reserved memory spaces to be reassigned or released based on current system requirements.
2Productivity
If reserved memory spaces are allocated for boot stages, then boot processes can execute, but memory cannot be reallocated for other purposes
Solution Approach 1:
The patent introduces a virtual interface as an intermediary layer between the physical memory and the boot stages. This virtual interface acts as a mediator that enables memory reallocation by providing a flexible mapping layer, allowing the system to allocate memory for boot processes when needed and reallocate it for other purposes when boot processes are complete.
Solution Approach 2:
The system transitions from static reserved memory allocation to dynamic memory allocation through the virtual interface. The memory map can be dynamically redefined at runtime, enabling the system to adapt memory usage based on current operational needs rather than being locked into fixed allocations.
3Device complexity
If a fixed memory layout is used, then memory allocation is simple, but memory utilization efficiency is reduced
Solution Approach 1:
The virtual interface serves as an intermediary that sits between the simple fixed memory layout and the complex dynamic allocation requirements. It provides a layer of abstraction that simplifies the interface for boot stages while enabling complex memory reallocation and utilization optimization at runtime.
Solution Approach 2:
The patent segments the memory management into distinct layers: a simple fixed memory layout at the physical level and a virtual interface layer that handles complex allocation and reallocation logic. This segmentation allows each layer to optimize for its specific requirements without compromising the other.
Data Source
AI summary
An information handling system includes a hardware processor, a memory device operatively coupled to a serial peripheral interface (SPI) chip and the hardware processor. The SPI chip interfaces the hardware processor executing plural stages of boot modules during a boot process of the information handling system with allocated, reserved portions of the memory device for each stage of boot module executed in pre-boot, boot, and runtime via a virtual memory interface generated by execution of an original equipment manufacturer (OEM)-defined agnostic memory allocation module. The hardware processor executes the OEM defined agnostic memory allocation firmware to redefine the virtual memory interface for each allocated reserved portion of the memory device at each of the plural stages of the boot modules that are executed from pre-boot, through boot, and to runtime to provide adjustments to allocated, reserved portions of memory for later stages of executed plural stages of the boot modules.