Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When a page fault occurs the MMU raises and exception (interrupt). The OS stops the current processes and addresses this raised interrupt.
1) Does this mean that (for 68K architecture where there are 7 interrupt lines with 7th being un-maskable) the interrupt generated by the MMU is at level 7?
2) Also, what if there a really important process going on (that does not require the virtual addressed word’s data) when the interrupt is raised? What does the OS do?
An exception is not necessarily an interrupt. Interrupts are exceptions, but there are exceptions which are not interrupts.
The page fault exception is an exception, but not an interrupt.
Non-interrupt exceptions are handled always. The page fault exception is a synchronous exception, when it occurs it’s because the current code raised it, so the OS should handle it in the appropriate way (which may include panicking because there has been a page fault in a section of code where it was not expected).