Hi Tung,
You have a bunch of test and trace CPUs available under
src/cpu/{testers,trace}. The trace CPU replays traces recorded using DerivO3CPU
while the testers generate synthetic traffic. If you want to replay your own
traces, you must either convert them to gem5 traces or implement your own
Hi Gabriel
Thank you for the answer, can we simulate coherent NoC with CHI protocol as
a stand-alone using traces?
Best
/Tung
On Sun, Oct 10, 2021 at 11:59 PM Gabriel Busnot via gem5-users <
gem5-users@gem5.org> wrote:
> Hi,
>
> Yes, there is. Look at the CHI protocol. It is compiled by default
I was able to fix the /sbin/init issue, which was separate. I got
./m5term going and that helped me resolve the issue (such a useful tool—I’m
glad I know about it now). Thank you!
On Mon, Oct 18, 2021 at 3:25 PM Reiko Matsuda-dunn <
reiko.matsudad...@colorado.edu> wrote:
> Thanks Jason! I'm tryin
Hi,
It's not clear from the error log where the problem is, but it does
indicate that qemu failed to start. My suggestion is to check the path of
the qemu binary (i.e. this line
https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/develop/src/parsec/disk-image/parsec/parsec.json#44).
I
