Method for managing memory space during system initialization
View Patent ↗A method for managing use of a fixed memory space of a computer system is provided. The computer system interfaces with controllers for managing operation of devices that operate with the computer system. The method includes determining whether sufficient memory is allocated in the fixed memory space for initializing code for the controllers, and jumping to swappable portion of the fixed memory space. The method also includes executing code in the swappable portion of the fixed memory space. The method further includes loading additional code needed to initialize the controllers from an external memory chip to the fixed memory space where the additional code is executed to complete initialization of the controllers of the computer system.
1. A method to optimize memory resources after loading of an initialization code and a runtime code into an Option ROM space, comprising:
determining if the memory resources are available to run a configuration code during an initialization process, wherein the memory resources include extended memory, conventional memory, and the Option ROM space wherein; and
if the extended memory, the conventional memory, and the Option ROM space are not available;
a) running a portion of the initialization code located in a swappable space of the Option ROM space,
b) copying the configuration code into the swappable space over the portion of the initialization code,
c) running the configuration code in the swappable space of the Option ROM space,
repeating operations b) and c) if additional configuration code is to be run, wherein, if the extended memory, the conventional memory, and the Option ROM space are available, the swappable space of the Option ROM space is not used for running the configuration code.
2. The method as recited in claim 1 , wherein determining if the memory resources are available to run the configuration code during the initialization process includes, determining whether an interrupt has been initiated to run the configuration code.
3. The method as recited in claim 2 , wherein determining the availability of the extended memory is done by a memory allocator, the memory allocator checking to see if the interrupt has been initiated.
4. The method as recited in claim 1 , wherein running the portion of the initialization code includes,
jumping from a jump space to the swappable space to run the portion of the initialization code.
5. The method as recited in claim 4 , wherein copying the configuration code into the swappable space includes returning to the jump space after the portion of the initialization code has been run.
6. The method as recited in claim 5 , wherein running the configuration code includes jumping to the swappable space to run the configuration code.
7. The method as recited in claim 1 , wherein the copying of the configuration code is from a flash memory device to the Option ROM space.
8. A method for managing use of a fixed memory space of a computer system, the computer system configured to interface with controllers for managing operation of devices that operate with the computer system, comprising:
determining whether sufficient memory is allocated in a conventional memory, an extended memory, and an Option ROM for initializing the controllers;
when sufficient memory is not allocated in the conventional memory, the extended memory, and the Option ROM,
executing a portion of a code needed to initialize the controllers, wherein the portion of the code is located in a swappable portion of the Option ROM; and
loading an additional code needed to initialize the controllers from an external memory chip to the swappable portion of the Option ROM, wherein loading the additional code includes copying the additional code over the portion of the code previously executed in the swappable portion of the Option ROM, the additional code being executed to complete initialization of the controllers of the computer system, wherein, if the extended memory, the conventional memory, and the Option ROM are available, the swappable portion of the Option ROM is not used for running the additional code.
9. The method as recited in claim 8 , wherein the additional code is configuration code.
10. The method as recited in claim 8 , wherein determining whether sufficient memory is allocated is done by a memory allocator in a memory allocator space within an initialization space.
11. The method as recited in claim 8 , wherein the external memory chip is a flash memory device.
12. The method as recited in claim 8 , wherein executing the portion of code needed to initialize the controllers includes, jumping to the swappable portion of the Option ROM.