I will be trying to reproduce this soon I hope, but in the meantime, can you check things like:
- does /proc/cpuinfo show multiple cpus? - do kernel boot messages show multiple cpus being brought up? - does the problem happen for other content, or just PARSEC? E.g. you could try to install and run "stress -c 16", which is simple and definitely uses multiple threads - play around with process affinity, e.g. https://unix.stackexchange.com/questions/23106/how-to-limit-a-process-to-one-cpu-core-in-linux On Sun, Apr 22, 2018 at 4:14 AM, Peter De Groot <[email protected]> wrote: > Hello, > > I ran the blackscholes PARSEC benchmark on an ARM big.LITTLE configuration > with 2 big cores and 2 small cores. It seems cpus0 in the bigCluster is the > only one that has cache data according to stats.txt. The relevant entries > for the other CPUs are either missing or NaN. Do you have any ideas as to > how I could get the cache information for the other CPUs, or if the > simulation is even working correctly? > > I simulated with this command: ./build/ARM/gem5.opt > configs/example/arm/fs_bigLITTLE.py --big-cpus=2 --little-cpus=2 --disk > /home/peter/Desktop/aarch/disks/expanded-linaro-minimal-aarch64.img > --bootscript > /home/peter/Desktop/arm-gem5-rsk/parsec_rcs/blackscholes_simlarge_4.rcS > --kernel /home/peter/Desktop/linux/vmlinux --caches > > The rcS file used is: > > #!/bin/bash > > PARSEC_DIR="/home/root/parsec-3.0" > cd $PARSEC_DIR > pwd > > source ./env.sh > parsecmgmt -a run -p blackscholes -c gcc-hooks -i simlarge -n 4 > m5 exit > > I copied the stats file to Pastebin here: https://pastebin.com/BAvbSmiv > > Thanks, > Peter de Groot > > > _______________________________________________ > 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
