How page faults are handled with Page Size Extension?
I was trying to understand the concept of Page Size Extension, used in x86 processor but was not able to relate it with the page fault mechanism. From my understanding, when a page fault occurs, the virtual address is written in a register and an error code is pushed onto the stack. But if we are using page size extension, then how does the page fault handler comes to know what page size needs to be allocated.Can anyone help me with this?
There is a bit in the page directory. Intel calls this the PS bit. (Page size?) If the bit is set, it is a large page. If clear, a small page. While Intel allows both page sizes to be in use simultaneously, I would wager that few OS implementations would support mixed page sizes.
What are the drawbacks of Lamport's happens-before algorithm?
How to decide if a “Device ” need an Operating System or not
Difference between shared memory IPC mechanism and API/system-call invocation
Is it possible to create an OS that can run all application?
Can't understand Belady's anomaly
Paging: Basic, Hierarchical, Hashed, and Inverted
What is the difference between kernel stack and user stack?
Ridiculous Question, but can I have SAS return the computer's volume level?
Why is an operating system software loaded from hard disk than from a rom chip? [closed]
What sort of things can cause a whole system to appear to hang for 100s-1000s of milliseconds?
How to make an bootable iso(not cd or flash drive) for testing your own boot loader?
stack overflow method
How does communication occur in java through TCP sockets on the same machine
What happens when you overwrite a memory-mapped executable?
Valid characters for environment variables across operating systems