Physical Address Extension

From Wikipedia, the free encyclopedia

In computing, Physical Address Extension (PAE) is a feature to allow 32-bit x86 central processing units (CPUs) to access a physical address space (including random access memory and memory mapped devices) larger than 4 gigabytes. First implemented in the Intel Pentium Pro in 1995, it was extended by AMD to add a level to the page table hierarchy, to allow it to handle up to 52-bit physical addresses, add NX bit functionality, and make it the mandatory memory paging model in long mode.[1] PAE is supported by Intel Pentium Pro and later Pentium-series processors except most 400 MHz-bus versions of the Pentium M.[citation needed ] It is also available on AMD processors such as the AMD Athlon and later AMD processor models.

Contents
1 Design 2 Page table structures 3 Support 4 Operating system support 4.1 Microsoft Windows 4.2 Mac OS X 4.3 Linux 4.4 Others 5 See also 6 References 7 External links

Design
x86 processor hardware-architecture is augmented with additional address lines used to select the additional memory, so physical address size increases from 32 bits to 36 bits. This increases the physical memory addressable by the system from 4 GB to 64 GB. The 32-bit size of the virtual address is not changed, so regular application software continues to use instructions with 32-bit addresses and (in a flat memory model) is limited to 4 gigabytes of

virtual address space. Operating systems supporting this mode use page tables to map the regular 4-GB address space into the physical memory, which depending on the operating system may be as big as 64 GB. The mapping is typically applied separately for each process, so that the extra memory is useful even though no single regular application can access it all simultaneously.

Page table structures

In traditional 32-bit protected mode, x86 processors use a two-level page translation scheme, where the control register C R 3points to a single 4 kB long page directory divided into 1024 4 byte entries that point to 4 kB long page tables, similarly consisting of 1024 4 byte entries pointing to 4 KB long pages. Enabling PAE (by setting bit 5, P A E , of the system register C R 4 ) causes major changes to this scheme. By default, the size of each page remains as 4 kB. Each entry in the page table and page directory grows to 64 bits (8 bytes) rather than 32 bits to allow for additional address bits. However, the size of tables does not change, so both table and directory now have only 512 entries. Because this allows only one quarter of the entries of the original scheme, an extra level of hierarchy has been added, so CR3 now points to the Page Directory Pointer Table, a short table which contains pointers to 4 page directories. The entries in the page directory have an additional flag in bit 7, named P S(for page size). If the system has set this bit to 1 , the page directory entry does not point to a page table, but to a single large 2 MB page (Page Size Extension). The NX bit is another flag in the page directory, in bit 63, to mark pages as no execute. Because the 12 least significant bits of the page table entry's 64 bits are either similar flags or are available for OS-specific data, a maximum of 52 bits are available to address 252 bytes, or 4 petabytes, of physical memory. On x86-64 processors in native long mode, the address translation scheme uses PAE but adds a fourth table, the 512-entry page-map level 4 table, and extends the page directory pointer table to 512 entries instead of the original 4 entries it has in protected mode. Currently 48 bits of virtual page number are translated, giving a virtual address space of up to 256 TB.[2] In the page table entries, in the original specification, 40 bits of physical page number are implemented. Page table structures

No PAE, 4 kB pages

No PAE, 4 MB pages

PAE with 4 kB pages

PAE with 2 MB pages

Support
See also: CPUID Software can identify via the C P U I Dflag P A Ewhether a CPU supports PAE mode or not. A free-of-charge program for Microsoft Windows is available which will list many processor capabilities, including PAE support.[3] In Linux, commands such as c a t/ p r o c / c p u i n f ocan list the p a eflag when [4] present, as well as other tools such as the SYSLINUX Hardware Detection Tool. To use PAE, motherboard and operating system support is required.

Operating system support

Microsoft Windows

Microsoft Windows implements PAE if booted with the appropriate option, but current 32-bit desktop editions enforce the physical address space within 4 GB even in PAE mode. According to Geoff Chappell, Microsoft limits 32-bit versions of Windows to 4 GB as a matter of its licensing policy,[5] and Microsoft Technical Fellow Mark Russinovich says that some drivers were found to be unstable when encountering physical addresses above 4 GB.[6] Unofficial kernel patches for Windows Vista and Windows 7 32-bit are available[7] [8] that break this Microsoft enforced limitation, though the stability is not guaranteed. These tools increase the RAM limit of the 32-bit version of Windows 7 to 64 GB. For 32-bit application software which needs access to more than 4 GB of RAM, operating systems may provide some special mechanisms in addition to the regular PAE support. On Windows this mechanism is called Address Windowing Extensions. The x86 versions of the following releases of Microsoft Windows support PAE:[9][10][11] Itanium versions of these operating systems (if they exist) do not use PAE because the Itanium does not need nor implement PAE. x86-64 editions of Windows always implement PAE, because it is a mandatory feature of long mode. The following table shows the hard memory limits for release versions of Microsoft Windows on the x86/x64 architecture [12]: Windows Version [13] Windows 2000 Professional, Server Windows 2000 Advanced Server Windows 2000 Datacenter Windows XP Starter Windows XP Home & Media Center Windows XP Professional Windows Server 2003 Web Windows Server 2003 Small Business, Home, Storage Windows Server 2003 Storage Server Windows Server 2003 R2 Standard Edition Windows Server 2003 Standard Edition (SP1) Windows Server 2003 Standard Edition (SP2) Windows Server 2003 Enterprise Edition (SP1) Windows Server 2003 R2 Enterprise Edition 32-bit editions 64-bit editions 4 GB 8 GB 32 GB 512 MB 4 GB 4 GB 2 GB 4 GB 4 GB 4 GB 4 GB 4 GB 16 GB with 4GT 64 GB
N/A N/A N/A N/A N/A

128 GB
N/A N/A N/A

32 GB 32 GB 32 GB
N/A

1 TB

Windows Server 2003 Datacenter (SP1) Windows Server 2003 R2 Datacenter (SP1) Windows Server 2003 R2 Datacenter (SP2) Windows Vista Starter Windows Vista Home Basic Windows Vista Home Premium Windows Vista Business, Enterprise, Ultimate Windows Server 2008 Standard, Web Windows Server 2008 Enterprise, Datacenter Windows 7 Starter Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional, Enterprise, Ultimate Windows Server 2008 R2 Foundation Windows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise, Datacenter, or Itanium Windows 8 Windows 8 Pro Windows Server 2012 Foundation Windows Server 2012 Essentials Windows Server 2012 Standard, Datacenter

128 GB 128 GB 128 GB 1 GB 4 GB 4 GB 4 GB 4 GB 64 GB 2 GB 4 GB 4 GB 4 GB

N/A N/A N/A

N/A

1 TB 2 TB
N/A

8 GB 16 GB 128 GB 32 GB 2 TB
N/A

8 GB 16 GB 192 GB 8 GB 32 GB 2 TB 128 GB 512 GB 32 GB 64 GB 4 TB

4 GB 4 GB
N/A N/A N/A

Values for Windows Server 2008 64-bit also apply to Windows Server 2008 R2 (which dropped 32-bit support). Values for Windows Server 2003 64-bit depend on: 1. service pack level 2. the release being R2 or not

The highest possible values appear here. The original releases of Windows XP and Windows XP SP1 used PAE mode to allow RAM to extend beyond the 4 GB address limit. However, it led to compatibility problems with 3rd party drivers which led Microsoft to remove this capability in Windows XP Service Pack 2. Windows XP SP2 and later, by default, on processors with the no-execute (NX) or execute-disable (XD) feature, runs in PAE mode in order to allow NX.[14] The no execute (NX, or XD for execution disable) bit resides in bit 63 of the page table entry and, without PAE, page table entries on 32-bit systems have only 32 bits; therefore PAE mode is required in order to exploit the NX feature. However, "client" versions of 32-bit Windows (Windows XP SP2 and later, Windows Vista, Windows 7) limit physical address space to the first 4 GB for driver compatibility [6] and licensing[5] reasons, even though these versions do run in PAE mode if NX support is enabled. Windows 8 will only run on processors which support PAE, in addition to NX and SSE2.[15]

Mac OS X
Intel versions of Mac OS X support PAE. Versions 10.4.4 through 10.5.8 of Mac OS X run on both x86 and PowerPC processors. Version 10.6 and 10.7 version of OS X only run on an x86 processors. So far, all x86 Macs have used Intel (not AMD) CPUs. OS X versions that are compatible with x86 fully support PAE and the NX bit on all Intel Macs. Mac Pro and Xserve systems can use up to 64 GB of RAM. The Mac OS X 10.5 (Leopard) kernel remains 32-bit. Mac OS X 10.6 (Snow Leopard) can be booted into a 64-bit version of the kernel on certain systems; Mac OS X 10.7 (Lion) and Mac OS X 10.8 (Mountain Lion) ship with a 64-bit enabled kernel by default.[16]

Linux
See also: Executable space protection#Linux The Linux kernel includes full PAE mode support starting with version 2.3.23,[17] enabling access of up to 64 GB of memory on 32-bit machines. A PAE-enabled Linux kernel requires that the CPU also support PAE. The Linux kernel supports PAE as a build option and major distributions provide a PAE kernel either as the default or as an option. As of 2009,[18] some common Linux distributions have started to use a PAE-enabled kernel as the distribution-specific default.[18] As of 2012, common Linux distributions have stopped distributing non-PAE kernels, thus making PAE hardware mandatory - examples being Red Hat Enterprise Linux / CentOS from version 6.0, Ubuntu (and derivatives like Linux Mint) from 12.10.[19] Fedora and Debian still distribute both PAE and non-PAE kernels.

Others
FreeBSD and NetBSD also support PAE as a kernel build option. FreeBSD supports PAE in the 4.x series starting with 4.9, in the 5.x series starting with 5.1, and in all 6.x and later releases. Support requires the kernel P A Econfiguration-option. Loadable kernel modules can only be

loaded into a kernel with PAE enabled if the modules were built with PAE enabled; the binary modules in FreeBSD distributions are not built with PAE enabled, and thus cannot be loaded into PAE kernels. Not all drivers support more than 4 GB of physical memory; those drivers won't work correctly on a system with PAE.[20] Solaris supports PAE beginning with Solaris version 7. However, third-party drivers used with version 7 which do not specifically include PAE support may operate erratically or fail outright on a system with PAE.[21] Haiku added initial support for PAE sometime after the R1 Alpha 2 release. With the release of R1 Alpha 3 PAE is now officially supported.

See also
Page Size Extension PSE-36 an alternative to Physical Address Extension Architecture of Windows NT 3 GB barrier limitations preventing access to 4 GB RAM ARM Cortex-A15 MPCore with Large Physical Address Extensions (LPAE)

References
1. ^ "AMD64 Architecture Programmer's Manual Volume 2: System Programming" (http://support.amd.com/us/Processor_TechDocs/24593.pdf) (PDF). AMD64 Architecture Programmer's Manual. Advanced Micro Devices. November 1, 2009. pp. 124143. Retrieved February 3, 2010. "Long-mode page translation requires the use of physical-address extensions (PAE). Before activating long mode, PAE must be enabled by setting C R 4 . P A Eto 1 . Activating long mode before enabling PAE causes a general-protection exception (#GP) to occur." 2. ^ AMD Corporation (May 2011). "Volume 2: System Programming" (http://support.amd.com/us/Embedded_TechDocs/24593.pdf) (pdf). AMD64 Architecture Programmer's Manual. AMD Corporation. Retrieved 2011-10-29. 3. ^ Microsoft Sysinternals: Coreinfo (http://technet.microsoft.com/en-us/sysinternals/cc835722) 4. ^ "Detecting your Hardware" (http://www.gentoo-wiki.info/Detecting_your_Hardware). Gentoo. October 8, 2008. Retrieved 2013-04-28. 5. ^ a b http://www.geoffchappell.com/notes/windows/license/memory.htm 6. ^ a b Mark Russinovich (2008-07-21). "Pushing the Limits of Windows: Physical Memory" (http://blogs.technet.com/markrussinovich/archive/2008/07/21/3092070.aspx). Retrieved 2010-07-11. 7. ^ "32Vista/Win 7 4GB ReadyFor4GB" [ReadyFor4GB: Vista/Win 7 32-bit patch for big memory of 4GB] (http://zhdeepxw.blogspot.com/2009/04/readyfor4gb.html) (in Chinese). 2009-04-26. Retrieved 2011-03-17. 8. ^ Unawave. "Windows 7 32-bit with full 4 GB or 8 GB RAM support" (http://www.unawave.de/windows-7-tipps/32-bit-ram-barrier.html?lang=EN). Retrieved 2010-07-11. 9. ^ "Memory Limits for Windows releases" (http://msdn2.microsoft.com/en-us/library/aa366778.aspx). Microsoft. December 5, 2007. Retrieved 2007-1210.

10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21.

10. ^ "Intel Physical Addressing Extensions (PAE) in Windows 2000" (http://support.microsoft.com/kb/268363/). Microsoft. October 26, 2007. Retrieved 2007-12-29. ^ "Overview of Windows Server 2003 R2 Datacenter Edition" (http://technet.microsoft.com/en-au/windowsserver/bb429508.aspx). Microsoft. Unknown. Retrieved 2009-05-15. ^ "Memory Limits for Windows Releases" (http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx). MSDN. Retrieved May 16, 2013. ^ "Memory Limits for Windows Releases" (http://msdn.microsoft.com/en-us/library/aa366778.aspx). Microsoft. March 25, 2010. Retrieved 2010-04-05. ^ "The RAM reported by the System Properties dialog box and the System Information tool is less than you expect in Windows Vista or in Windows XP Service Pack 2 or later version (MSKB 888137)" (http://support.microsoft.com/kb/888137). Knowledge Base. Microsoft. Retrieved 2009-01-30. ^ How To Check If Your Processor Supports PAE, NX And SSE2 For Windows 8 Installation (http://www.technize.net/how-to-check-if-your-processorsupports-pae-nx-and-sse2-for-windows-8-installation/?ModPagespeed=noscript) ^ "Road to Mac OS X 10.6 Snow Leopard: 64-Bits" (http://www.appleinsider.com/articles/08/08/26/road_to_mac_os_x_10_6_snow_leopard_64_bits.html). 2008-09-26. Retrieved 2008-09-26. ^ "2.3.23-pre4 x86 64GB RAM changes [HIGHMEM patch] explained a bit" (http://lkml.indiana.edu/hypermail/linux/kernel/9910.2/0542.html). ^ a b "x86 Specifics for Fedora 11" (http://docs.fedoraproject.org/en-US/Fedora/11/html/Release_Notes/sect-Release_NotesArchitecture_Specific_Notes.html#sect-Release_Notes-x86_Specifics_for_Fedora). ^ "EnablingPAE" (https://help.ubuntu.com/community/EnablingPAE). Retrieved 2013-04-28. ^ "FreeBSD PAE(4) man page" (http://www.FreeBSD.org/cgi/man.cgi?query=pae&sektion=4). 2003-04-08. Retrieved 2007-11-26. ^ "Solaris 7 5/99 Release Notes (Intel Platform Edition), Appendix B: Hardware Compatibility List and Device Configuration Guide (Intel Platform Edition) 5/99" (http://docs.sun.com/app/docs/doc/806-0225/6j9ji3kj2). 1999. Retrieved 2007-11-26.

External links
Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 3A: System Programming Guide, Part 1 (http://www.intel.com/Assets/PDF/manual/253668.pdf) Windows PAE entry on MSDN Library (http://msdn2.microsoft.com/en-us/library/aa366796.aspx) Windows PAE entry on Microsoft knowledge base (http://support.microsoft.com/?kbid=291988) Retrieved from "http://en.wikipedia.org/w/index.php?title=Physical_Address_Extension&oldid=555608598" Categories: X86 architecture Virtual memory Memory management X86 memory management This page was last modified on 18 May 2013 at 04:47. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.