OSDev.org

osdevwiki wrote: 31 4 0
+-----+-...-+-----+-----+-----+-----+-----+-----+
| Reserved | I/D | RSVD| U/S | W/R | P |
+-----+-...-+-----+-----+-----+-----+-----+-----+
P: When set, the fault was caused by a protection violation.
When not set, it was caused by a non-present page.
W/R: When set, write access caused the fault; otherwise read access.
U/S: When set, the fault occurred in user mode; otherwise in supervisor mode.
RSVD: When set, one or more page directory entries contain reserved bits which are set to 1.
This only applies when the PSE or PAE flags in CR4 are set to 1.
I/D: When set, the fault was caused by an instruction fetch.
This only applies when the No-Execute bit is supported and enabled.

loki2441 wrote:I am a very curious about how the instruction fetch page fault is generated? I would really appreciate it if someone could give me a example.

loki2441 wrote:And also how this kind of page fault will be handled?

• determine if the access should have been allowed:
  • If it should've been allowed, fix stuff so that the access will work (e.g. load the page from swap space or memory mapped file) and return (retry the instruction that caused the exception)
  • If it shouldn't be allowed (e.g. the code that was running crashed), pass control to some sort of crash handler (which might do "blue screen of death", or terminate the process, or send a signal to the process, or do a core dump, or whatever).