You observed that the check on line 471 in tlb.cc did not seem to be the one causing the fault in the case you were looking at. It occurs to me that the line 471 check is for a *resident* page. If the page is *not* resident, some other check would apply, and the fault might be raised when the OS examines the PTE to determine what to do with a disallowed access to a non-resident page.
Could that be the scenario you were looking at? That would indeed seem to be more involved, though at the point gem5 does the interrupt for a non-resident page (one not in the TLB) you might be able to more directly do a check of the PTE. To do that you would need to emulate walking the page tables (hoping that all the relevant page table pages are themselves resident). Yes, possibly a bit of a mess ... EM _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
