Hi Javed,
I don't have a reliable answer for you. It is possible that the current CHI
cache implementation cannot be shared, although it would surprise me. I would
suggest you to ping Tiago Mück who wrote this stuff to ask him about that.
On your side, you can dig in the ProtocolTrace flag outp
Hello Gabriel
Many thanks for your thoughts.
Just checking, is Tiago's email tiago.m...@arm.com?
Best regards
J.Osmany
-Original Message-
From: Gabriel Busnot via gem5-users [mailto:gem5-users@gem5.org]
Sent: 10 August 2021 09:59
To: gem5-users@gem5.org
Cc: Gabriel Busnot
Subject: [g
Hi all,
I am having trouble with gem5 SE mode running a simple memory copy
microbenchmark (https://github.com/BTone/cagbench) that uses a configurable
number of worker threads that all wait to start and finish at a barrier.
I have found that using a pthread_barrier is not working, as once all
wor
I am having the following error in gem5. I've tested it on X86 only and it
causes fatal error.
Command:
sudo ./build/X86/gem5.opt configs/example/se.py --cmd /usr/bin/python3.5
--options "train.py --scenario simple" --caches --l2cache
--cpu-type=TimingSimpleCPU --mem-type=DDR3_1600_8x8 --mem-size
Host OS: Ubuntu 12.04 LTS
Host CPU: Intel i7-2600 3.40 GHz
I'm trying to debug an x86 application on an O3CPU using syscall emulation,
but static_inst.cc panics or runs into an assertion error. Ideas for how I
can debug or solve this issue?
Example command 1 (causing panic): build/X86/gem5.opt --
Correction:
The host Operating System is Ubuntu 20.04.2 LTS
The host CPU is Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
I built gem5 using `scons build/X86/gem5.opt`, from the latest stable
branch (v21.1.0.0)
___
gem5-users mailing list -- gem5-users@gem5.or
Please give this a try:
https://gem5-review.googlesource.com/c/public/gem5/+/49183
On Tue, Aug 10, 2021 at 9:37 PM Deric Cheung via gem5-users <
gem5-users@gem5.org> wrote:
> Host OS: Ubuntu 12.04 LTS
> Host CPU: Intel i7-2600 3.40 GHz
>
> I'm trying to debug an x86 application on an O3CPU using
