A page fault (sometimes #pf or pf) is a trap to the software raised by the hardware when a program accesses a page that is mapped in the virtual address space, but not loaded in physical memory. In the typical case the operating system tries to handle the page fault by making the required page accessible at a location in physical memory or kills the program in the case of an illegal access. The hardware that detects a page fault is the memory management unit in a processor. The exception handling software that handles the page fault is generally part of the operating system.
Contrary to what the name 'page fault' might suggest, page faults are not always errors and are common and necessary to increase the amount of memory available to programs in any operating system that utilizes virtual memory, including Microsoft Windows, Unix-like systems (including Mac OS X, Linux, *BSD, Solaris, AIX, and HP-UX), and z/OS. Microsoft uses the term hard fault in more recent versions of the Resource Monitor (e.g., Windows Vista) to mean 'page fault'.
Read more about Page Fault: Handling Illegal Accesses and Invalid Page Faults, Performance
Famous quotes containing the words page and/or fault:
“I asked myself, “Is it going to prevent me from getting out of here? Is there a risk of death attached to it? Is it permanently disabling? Is it permanently disfiguring? Lastly, is it excruciating?” If it doesn’t fit one of those five categories, then it isn’t important.”
—Rhonda Cornum, United States Army Major. As quoted in Newsweek magazine, “Perspectives” page (July 13, 1992)
“If the dignity as well as the prestige and influence of the United States are not to be wholly sacrificed, we must protect those who, in foreign ports, display the flag or wear the colors of this Government against insult, brutality, and death, inflicted in resentment of the acts of their Government, and not for any fault of their own.”
—Benjamin Harrison (1833–1901)