See the list of debug flags here:
https://gem5.googlesource.com/public/gem5/+/master/src/mem/ruby/SConscript
Also, running "gem5 --debug-help" will list all of the debug flags.
There's no way to know what flags will be most helpful. You should play
around with them to find out.
Finally, I'm not
Hi Jason,
Can you tell me about more debug flags other than ProtocolTrace that can be
used to trace the addresses in caches.
regards,
Muhammad
On 14 February 2018 at 22:05, Jason Lowe-Power wrote:
> Hi Muhammad,
>
> Unfortunately, debugging these kinds of issues is *incredibly* difficult.
Hi Muhammad,
Unfortunately, debugging these kinds of issues is *incredibly* difficult.
Especially when they only occur during full system execution.
I would try grepping for the address that is deadlocking and starting by
tracing the address from where it originally issued through the cache
hiera
Hi Jason,
Last email was incomplete sorry for that.
I am running following system,
./build/ARM/gem5.debug --debug-flags ProtocolTrace configs/example/fs.py
--l1d_size=32kB --l1i_size=32kB --num-l2caches 4 --l2_size=1MB
--cacheline_size=64 --machine-type=VExpress_GEM5_V1 --kernel
/home/khilji
