Configuring System Memory

The amount of RAM allocated to the kernel for an operating system (OS) use can be configured in four different areas:

• Config.bib Customization
• MainMemoryEndAddress Customization
• OEMGetExtensionDRAM Customization
• pNKEnumExtensionDRAM Customization

In each case, the memory identified requires that the physical-to-virtual mapping tables are initialized so that the kernel can implement the proper support to use the memory.

In the SHx and MIPS families, the CPU defines this mapping, and the kernel requires no additional information.

In the x86 and ARM families, you must set up the proper entries in OEMAddressTable to identify your RAM regions. You should create RAM entries for the largest possible amount of RAM that would be present on the device. This help avoid the need to change the OEM adaptation layer (OAL) if you add more memory. If RAM is not mapped during the boot process through OEMAddressTable, it can be mapped later by calling CreateStaticMapping or NKCreateStaticMapping.

However memory is specified to the kernel, the kernel will create a single pool that will be used for all memory allocations.

See Also

Customizing Memory | How to Configure and Build an OS Image for a CEPC

Last updated on Wednesday, April 13, 2005

© 2005 Microsoft Corporation. All rights reserved.