Hi,
I have some sad news... I reverted that patch, but I again met deadlocks in the
develop branch.
The key error message is as follows:
```
build/GCN3_X86/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...)
build/GCN3_X86/mem/ruby/system/Sequencer.cc:240: panic: Possible Deadlock
d
Hi Yao,
Long-term, yes, the performance of gem5 is something that is important to
improve! We often hear this as one of our most wanted features. However,
because of the way gem5 was designed and has evolved over time,
*parallelizing* it will be very, very difficult. There are just too many
places
Hi Jason, hi Jonathan,
thanks a lot for pointing out SimPoint! I’m currently searching for details on
how to use SimPoint with gem5. Is it right that I need to run the benchmarks at
first using a timing CPU to take checkpoints at first? I guess (and hope) there
is a way to generate the Simpoint
