Hello, The classic memory model does not support the atomic memory accesses that X86 does. In FS you will have many situations where this behavior can be exposed, doing a simple cat /proc/cpuinfo will hang the simulation. The chances of your benchmark getting stuck are quite high. However I have seen some simulations finishing.
You can find more info on this at: http://comments.gmane.org/gmane.comp.emulators.m5.devel/18749 If you want to simulate caches with X86 and FS, Ruby is what works. ________________________________________ De: [email protected] [[email protected]] en nombre de Sanem Arslan [[email protected]] Enviado: sábado, 12 de abril de 2014 9:54 Para: gem5 users mailing list Asunto: [gem5-users] X86 FS with timing CPU Hi All, I want to build X86 full system with using timing cpu type. There is no problem in se mode, I can run codes in X86 se mode with timing cpu. However, I have encountered with problems in fs mode. The command that I have used is: /build/X86/gem5.debug configs/example/fs.py --num-cpus=4 --caches --l2cache -- --cpu-type=timing --disk-image=/home/sanem/full_system_images/disks/linux-x86.img --kernel=/home/sanem/full_system_images/binaries/x86_64-vmlinux-2.6.22.9.smp When I connect to the machine with m5term, it get stuck on a step and couldn't build the system although I waited for 1 day (without any error or panic) . Is there anyone who can build a X86 system with timing cpu? (BTW, I have encountered with errors when I used gem5.opt or gem5.fast for building X86 with timing cpu) On the other hand, I tried to build system with atomic type and take checkpoint. Then I restore the checkpoint with “--restore-cpu-type=timing” command. I have checked config.ini file and there are two types of cpu. First one is “cpuX” which is timing and the second one is “switch_cpuX” which is atomic. There are values for “switch_cpuX” but the values for “cpuX” is zero. As I see, it continues to run in atomic mode and “--restore-cpu-type” may not be work correctly. Moreover, I tried to change the cpu type of the checkpoint that I took in atomic to timing with “--cpu-type=timing” keyword. In this case, the program is sometimes run and sometimes get stuck again. Is there any problem in timing mode for X86 fs? Best, Sanem. _______________________________________________ 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
