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
Hello everyone,
I ran some simulations with Garnet and noticed that the dest_queueing_delay
is always 0. (Only the queueing_delay (queueing_latency) is printed in
stats.txt; queueing_delay is the sum of src_queueing_delay and
dest_queueing_delay.)
After checking the code and debug traces, I
I have the 21.1.0.2 version. So that’s why I have this problem. I actually need
to use the older version for now so I will downgrade < 11 python.
Thanks for your help,
Ioannis
On 29 Sep 2023, at 3:20 PM, Bobby Bruce wrote:
--
Dr. Bobby R. Bruce
Room 3050,
Kemper Hall, UC Davis
Davis,
CA,
--
Dr. Bobby R. Bruce
Room 3050,
Kemper Hall, UC Davis
Davis,
CA, 95616
web: https://www.bobbybruce.net
> On Sep 29, 2023, at 5:19 AM, Bobby Bruce wrote:
>
> What version of gem5 are you using? In the latest version, v23.0 (`git clone
> https://github.com/gem5/gem5.git`
Hello,
I tried what you suggested too and it does not work.
I actually found an issue in this link
https://gem5.atlassian.net/browse/GEM5-1295 . So I suspect this is why
python3.11 does not work. The version of gem5 I have is 2.0 . So I think it’s
best to stick with python3.8 until I can
Python 11 should work fine as far as i know.
Try removing your build directory and recompiling from scratch (`rm -rf build
&& scons build/ALL/gem5.opt`). gem5 can get confused if you've moved the build
directory across different machines or changed stuff in the machines
environment. This may
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:
Hello,
I am currently trying to locate the code that is used to squash instructions if a Page Table Fault is triggered in the O3 CPU.
After using the PageTableWalker Debug Flags, my current guess would be gem5/src/arch/x86/pagetable_walker.cc in line 199.
Furthermore I inspected the files in
