PCI hole

<h2 id="unavailable-memory">Unavailable memory</h2>
<p>The loss of usable memory caused by the PCI hole, when using <a href="/facts/Memory-mapped_I%2fO/PmLNFq01">memory-mapped I/O</a>, is caused by using the same address space for both physical memory and to communicate with hardware devices. Thus, installed hardware devices need some of the address space in order to communicate with the processor and system software. As 32-bit hardware has a total of four gigabytes of addressable memory,<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> some of the real physical memory of a 32-bit machine, when enough memory is installed, needs to be sacrificed by making it hidden so the devices have room to communicate.  Which part of physical memory becomes replaced with the device communication space depends upon the machine, but it is usually anything above 2.5 to 3.5 GB.
</p><p>The amount of system memory that is hidden and unavailable varies widely with the actual mainboard and chipset, the BIOS, the amount of physical memory, the amount of <a href="/facts/Video_RAM/jjt4zoQB">video RAM</a> installed on graphics cards, and the number and type of <a href="/facts/PCI_cards/n6CGuFvP">PCI cards</a> installed in the system. More than a gigabyte of 32-bit system memory can be unavailable when four gigabytes of physical memory and multiple 3D cards with large amounts of video memory are installed; on some mainboards, the hole is always at least one gigabyte in size regardless of the installed <a href="/facts/Expansion_card/QkWAPnxJ">expansion cards</a>.
</p>
<h2 id="physical-address-extension">Physical address extension</h2>
<p>A workaround first developed in the Pentium Pro, known as <a href="/facts/Physical_Address_Extension/aEr4tj4x">Physical Address Extension</a> (PAE), allows certain 32-bit operating systems to access up to 36-bit memory addresses, even though individual programs are still limited to operating within 32 bits of address space. Provided there is enough memory installed, each program can have its own four-gigabyte addressing space, together utilizing up to 64 gigabytes of memory across all programs.
</p><p>But PAE alone is not enough to address the PCI hole issue, as memory addresses and I/O PCI addresses are still overlapping somewhere between the 3rd and 4th gigabyte. A PAE compatible operating system together with a PAE compatible CPU cannot do better than accessing memory from the 1st to the 3rd gigabyte, then from the 5th to the 64th gigabyte. The PCI hole is still there. On a 4GB host, and in the absence of one or another additional workaround, PAE does nothing for accessing the ~1GB memory overlapped by the PCI I/O.
</p><p>PAE was fully supported in Windows XP up to the Service Pack 1 (SP1) release, but then withdrawn for SP2; the only 32-bit versions of <a href="/facts/Microsoft_Windows/bwhAhuSL">Microsoft Windows</a> to fully support this are certain high-end server versions of <a href="/facts/Windows_Server_2003/3vIJam5L">Windows Server 2003</a> and earlier; as of 2014, it is mainly in use by 32-bit <a href="/facts/Linux/9FvCKSTq">Linux</a> distributions; <a href="/facts/Ubuntu/0WDd7hkb">Ubuntu</a> has made it mandatory for its 32-bit version since 2013. Microsoft disabled the support in Windows XP SP2 and later operating systems because there were many compatibility problems with graphics card and other devices, which needed PAE-aware drivers, distinct from both standard 32-bit and later 64-bit drivers.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> Many versions of MS Windows can activate what is still called PAE for the purpose of using the <a href="/facts/NX_bit/MnBB93BK">NX bit</a>, but this no longer extends the address space.
</p>
<h2 id="filling-the-memory-hole">Filling the memory hole</h2>
<p>As stated earlier, in a 32-bit PAE-enabled and even in 64-bit systems, memory below and above the "memory hole" is available, but 512 MB to 1.5 GB of RAM is unavailable, around the 3rd gigabyte, because it uses their memory addresses required for devices. With the decreasing cost of memory this may not be a serious issue, but there are ways to regain access to the missing memory.
</p>
<h3>Mapping devices to addresses above 4 GB</h3>
<p>The limitations of the 32-bit PCI hole can affect purely 64-bit operating systems as the system BIOS must cater for all operating systems which are supported by the hardware (16-, 32-, and 64-bit operating systems all run on the same hardware). The BIOS must be able to boot mapping all devices below four gigabytes, although a 64-bit system does not require this. Many BIOSes can be configured by the user to fill the memory hole by mapping devices high up in the 64-bit address space, so long as the devices, their drivers, and the <a href="/facts/Chipset/0xU3kbVI">chipset</a> all support this. A machine configured this way cannot boot into a 16- or 32-bit operating system; only UEFI boot mode is supported.
</p>
<h3>Mapping memory to addresses above 4 GB</h3>
<p>Another way to remove the PCI hole, which is only useful for 64-bit operating systems and those 32-bit systems that support the Physical Address Extension method described above, is to "remap" some or all of the memory between the two- and four-gigabyte limits to addresses above four gigabytes. This needs to be supported by the chipset of the computer and can usually be activated in the BIOS Setup. This remapping works on the level of <a href="/facts/Physical_address/G01PUI6A">physical addresses</a>, unlike the higher-level remapping of <a href="/facts/Virtual_address/ILxbMjgv">virtual</a> to physical addresses that happens inside the <a href="/facts/CPU/Jxp1bqMV">CPU</a> core. Activating this for traditional 32-bit operating systems does more harm than good, as the remapped memory (often larger than the PCI hole itself) is unusable to such operating systems, even though e.g. <a href="/facts/Windows_Vista/IASEUCTB">Windows Vista</a> will show such memory to physically exist on the "System Properties" page.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/AGP_aperture/kmrNmn8U">AGP aperture</a></li>
<li><a href="/facts/3_GB_barrier/fRQwMtFP">3 GB barrier</a></li>
<li><a href="/facts/Expanded_memory/cYurvMxB">Expanded memory</a></li>
<li><a href="/facts/PSE-36/UG8myR82">PSE-36</a> –  an alternative to PAE on x86 processors to extend the physical memory addressing capabilities from 32 bits to 36 bits</li>
<li><a href="/facts/RAM_limit/PqNlsyPh">RAM limit</a></li></ul>
<h2 id="notes">Notes</h2>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>"Memory Hole in Large Memory X86 Based Systems" (PDF). techfiles.de. Sun Microsystems. May 19, 2014. Archived from the original (PDF) on July 19, 2011. Retrieved November 7, 2014. <a href="https://web.archive.org/web/20110719090913/http://techfiles.de/dmelanchthon/files/memory_hole.pdf" target="_blank">https://web.archive.org/web/20110719090913/http://techfiles.de/dmelanchthon/files/memory_hole.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>With 16 bits, two to the power of 16 equals to 65,536 different locations that can be addressed; with 32 bits it is 4,294,967,296 locations, while with 64 bits it is 18,446,744,073,709,551,616. <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Dansdata: What's with the 3Gb memory barrier? <a href="http://www.dansdata.com/askdan00015.htm" target="_blank">http://www.dansdata.com/askdan00015.htm</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
</ol>

PCI hole open-in-new

PCI hole