Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • Thanks. "“copied” pages are marked read-only. When a process tries to write to them, the CPU faults". Are the CPU faults page fault exception? Are they handled by the page fault service routine? Commented Oct 15, 2018 at 17:44
  • Thanks. When calling malloc(), how is the page table updated to the virtual address returned by the function? The virtual address can't be mapped to a physical memory address. Is the virtual address mapped to "null" or some other value, so that page fault can happen when access that virtual address? Commented Oct 15, 2018 at 22:04
  • In the case of vfork(), is the "copy on exec()" (as opposed to "copy on write") also based on page fault? (I guess no, exec() does the copy by itself without need of page fault handling.) Commented Oct 16, 2018 at 1:03
  • See my updated. Regarding “copy on exec()”, I’m not sure what you mean; could you clarify your question? Commented Oct 16, 2018 at 7:30
  • Here is what I meant by "copy on exec()": A process vfork() a child, then the child exec(), and exec() will allocate new space for the child. Is it correct that "copy on exec()" is not based on page fault, because exec() does the "copy" by itself without need of page fault handling? Commented Oct 16, 2018 at 17:41