y this.
Kind regards,
Robin
Gesendet: Montag, 09. Oktober 2023 um 14:29 Uhr
Von: "Yuan Yao via gem5-users"
An: "The gem5 Users mailing list"
Cc: "Yuan Yao"
Betreff: [gem5-users] Re: Squashing Instructions after Page Table Fault
Hi Robin,
The &quo
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
ilto:gem5-users@gem5.org>
An: "The gem5 Users mailing list" <mailto:gem5-users@gem5.org>,
yuan@it.uu.se<mailto:yuan@it.uu.se>
Cc: reverent.gr...@web.de<mailto:reverent.gr...@web.de>, "Eliot Moss"
<mailto:m...@cs.umass.edu>
Betreff: [gem5-users] R
er 2023 um 17:00 Uhr
Von: "Eliot Moss via gem5-users"
An: "The gem5 Users mailing list" , yuan@it.uu.se
Cc: reverent.gr...@web.de, "Eliot Moss"
Betreff: [gem5-users] Re: Squashing Instructions after Page Table Fault
On 10/4/2023 10:03 AM, reverent.green--- via g
On 10/4/2023 10:03 AM, reverent.green--- via gem5-users wrote:
Hi Yuan,
thank you very much for your detailed response. My understanding of the
fault handling in gem5 is getting better and better. Using debug flags, I
can trace the control flow during the execution of my code.
I am
quot;
Cc: "Yuan Yao"
Betreff: [gem5-users] Re: Squashing Instructions after Page Table Fault
Hi Robin,
If I understand it correctly, a Page Table Fault instruction is not squashed but *not executed*. The instruction generating a fault is marked ready to commit. Then, during the com
Hi Robin,
If I understand it correctly, a Page Table Fault instruction is not squashed
but *not executed*. The instruction generating a fault is marked ready to
commit. Then, during the commit phase, the fault generated by the instruction
is handled.
To explain this in more detail let
A short addition. I also couldn't find a specific check for the user/supervisor Page Table Attribute anywhere.
Are there parts in the code, where specific bits are checked or does gem5 uses some other kind of implementation here?
Gesendet: Freitag, 29. September 2023 um 12:04 Uhr
Von:
