Hi Anderson I think that now I understand your question because I have tried to simulate the "hello" test program (that comes with GEM5) using gem5.opt for the first time at FS Alpha and FS x86, and the surprising results are:
Architecture Simulation Time(*) ---------------------------------------------- ARM 4 CPUs 66m50.399s ALPHA 1 CPU >749m39.720s (unfinished) X86 1 CPU >675m49.498s (unfinished) ---------------------------------------------- (*) All tests running "alone" at same [Intel i7 Extreme]@[3.33GHz+16GB RAM] machine. It is really a strange FS behavior and I don't know how to explain that. Maybe the disk images (provided by GEM5 download page) are not lightweight enough to provide a good comparison between simulation time for these architectures running at FS mode. But I'm not sure if it could be the main reason. Regards Romulo On Tue, Jul 17, 2012 at 12:58 PM, Anderson Faustino < andersonfaust...@gmail.com> wrote: > Hi, Romulo. > > I didn't explain correct my problem, in my last message. There is no > problem with ALPHA. > > But, X86 doesn't boot with 4 O3CPU, the other cpus work fine, but 03CPU > doesn't. > > Yesterday, I started a boot: > > ---------------- > build/X86/gem5.opt configs/example/fs.py > --kernel=x86_64-vmlinux-2.6.22.9.smp --cpu-type=detailed --l2cache --caches > --script=run.sh -n 4 > ---------------- > > And until now it didn't finish. The process is stopped in: > > Initializing CPU#3 > Calibrating delay loop (skipped)... 3999.96 BogoMIPS preset > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 1024K (64 bytes/line) > Fake M5 x86_64 CPU stepping 01 > Brought up 4 CPUs > migration_cost=16 > > Until now, it took 1173 minutes. > > I really want to understand: why doesn't a configuration with 4 O3CPU boot > the system? But other works fine. > > Thanks. >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
