Hi
I am getting the same error. Tripti did you solve the problem?
I m more some questions on the options regarding fast forwarding.


1. I am using SPEC 2K6 benchmarks (SE Mode). I am interested in collecting
stats when actual benchmark runs. How will I know, when should I switch to
detailed mode? In Parsec, I can do that using m5 switchcpus in .rcS file
(just before the binary simulation starts?)


2. I am not sure what is the difference between -s and -F options. If I give
-F <>, CPU will switch to detailed mode right after <> that many
instructions? Then what purpose -s is solving? If -s and -w <> is given,
does it mean that after CPU switches to detailed mode, caches are warmed up
till that period and stats are not collected till that time?
Can I also checkpoint when CPU switches?

3. During timing CPU mode, are caches attached to the CPU?. If yes, are they
flushed when it switches to detailed mode?


Please clarify, as I couldn't understand these issues from the documentation
or code.

Thanks
---- Adwait
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

Reply via email to