Hi,
                Can anyone please confirm whether the O3PipeView is working 
properly in the least gem5 repo or its something wrong with me. It used to work 
earlier.

Currently while trying to generate the Pipeline  trace for ARM detailed CPU 
model, I am getting an empty trace.out file.

./build/ARM/gem5.opt --debug-flags=O3PipeView --debug-start=500000 
--debug-file=trace.out configs/example/se.py -cpu-type=detailed --caches -c 
nop.out -m 1000000

**** REAL SIMULATION ****
info: Entering event queue @ 0.  Starting simulation...
info: Increasing stack size by one page.
Exiting @ tick 1000000 because simulate() limit reached


ls -l m5out
drwxrwxr-x  3 pchakra1 pchakra1  4096 Jul 18 10:21 ./
drwxrwxr-x 15 pchakra1 pchakra1  4096 Jul 18 10:21 ../
-rw-rw-r--  1 pchakra1 pchakra1 11242 Jul 18 10:21 config.ini
-rw-rw-r--  1 pchakra1 pchakra1 30245 Jul 18 10:21 config.json
drwxrwxr-x  5 pchakra1 pchakra1  4096 Jul 18 10:21 fs/
-rw-rw-r--  1 pchakra1 pchakra1 71553 Jul 18 10:21 stats.txt
-rw-rw-r--  1 pchakra1 pchakra1     0 Jul 18 10:21 trace.out



The executable runs much beyond 1000000 ticks, so the start and end ticks looks 
correct to me. I've tried various start/end but nothing works! Has the usage 
changed lately?

What needs to be changed if I want to use the minorview with the Minor model 
instead of O3? I don't see corresponding debug-flags except "MinorCPU".


Regards,
Prasenjit
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to