Hi Abhishek,
I think when you check *m5out/config.ini*, you should look at
*switch.cpu* instead of *system.cpu*.
System.cpu is always initialized to AtomicSimpleCPU by se.py.
Switch.cpu is the one you indicate in options and the one whose stats
you should be looking at.
System.cpu instructions executed should be 0 unless you specify a number
of fast forward instructions.
All the best,
Carlos
On 5/2/20 17:14, Abhishek Singh wrote:
Hello Everyone,
I am using X86 ISA, Out of order CPU. I wanted to run a
multi-programmed workload using SMT
My command line 1 is:
./build/X86/gem5.opt configs/example/se.py -c
tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello
--caches --l2cache --l1d_size=32kB --l1i_size=32kB --l2_size=2MB
--l1d_assoc=8 --l1i_assoc=8 --l2_assoc=16 --cacheline_size=64
--cpu-type=DerivO3CPU --mem-type=DDR4_2400_8x8 --mem-size=8GB
--sys-clock='2.6GHz' --cpu-clock='2.6GHz' --smt
I am using commit *82f6d6e90.*
When I run the command and check *m5out/config.ini, *the *system.cpu*
parameter is AtomicSimpleCPU instead of DerivO3CPU.
I tried the command without smt and using "-n" to run on different cores
My command line 2 is:
./build/X86/gem5.opt configs/example/se.py -c
tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello
--caches --l2cache --l1d_size=32kB --l1i_size=32kB --l2_size=2MB
--l1d_assoc=8 --l1i_assoc=8 --l2_assoc=16 --cacheline_size=64
--cpu-type=DerivO3CPU --mem-type=DDR4_2400_8x8 --mem-size=8GB
--sys-clock='2.6GHz' --cpu-clock='2.6GHz' -n 2
The cpu being used is AtomicSimpleCPU instead O3CPU indicated by
m5out/config.ini, is there any problem with my command or is there an
error?
Best regards,
Abhishek
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
