It should work, although I generally use the checkpoint, restore, switch method when sampling. There might be a problem with fast- forwarding with multiple cpus. You should take a look at Simulation.py and see what happens after the atomic cpu exits. All the atompc cpus should be replaced with timing or detailed cpus and the atomic cpus should be deactivated. Are you sure you're specifying a different type of CPU after the switch?
Ali On Oct 24, 2008, at 6:17 AM, Shoaib Akram wrote: > I made some changes to memory system and collected data for several > uniprocessor experiemts.However, for multiprogramming workloads I > ran into this assertion at switch of cpus. > > m5.opt: build/ALPHA_SE/cpu/simple/atomic.cc:202: virtual void > AtomicSimpleCPU::resume(): Assertion `system->getMemoryMode() == > Enums::atomic' failed. > > Any idea whats wrong? I use --fast-forward=X --max-inst=Y to fast > forwarding. > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
