| 31. | On many systems, a program's virtual address may refer to data which is not currently in memory.
|
| 32. | Architectures that survived evolved over time to support larger virtual address spaces using memory segmentation or other mechanisms.
|
| 33. | A translation selected by the virtual address has its key compared to each of the protection key registers.
|
| 34. | To feed the execution units with instructions and data, there is a 16 KB two-way set virtual addresses.
|
| 35. | Virtual addresses 0 thru 15 are reserved to reference the corresponding general purpose register, and are not mapped.
|
| 36. | MIPS32 and MIPS32r2 support 32 bits of virtual address space and up to 36 bits of physical address space.
|
| 37. | If the tag of the incoming virtual address matches the tag in the TLB, the corresponding value is returned.
|
| 38. | MIPS64 supports up to 64 bits of virtual address space and up to 59 bits of physical address space.
|
| 39. | Relationship between pages addressed by virtual addresses and the pages in physical memory, within a simple address space scheme.
|
| 40. | Virtual memory requires the processor to translate virtual addresses generated by the program into physical addresses in main memory.
|
