Ruby checkpointing is protocol independent.
You must take the checkpoint using MOESI_hammer,
then you can restore it with any other protocol.


________________________________
De: [email protected] [[email protected]] en nombre de 
[email protected] [[email protected]]
Enviado el: miƩrcoles, 06 de noviembre de 2013 9:51
Para: gem5 users mailing list
Asunto: Re: [gem5-users] ruby MOESI_CMP_directory Invalid RubyRequestType

I got the result from document at http://gem5.org/Checkpoints

While creating checkpoints with Ruby memory model, it is necessary to use the 
MOESI hammer protocol. This is because checkpointing the correct memory state 
requires that the caches are flushed to the memory. This flushing operation is 
currently supported only with the MOESI hammer protocol.

And I want to know is there any way for using checkpoint with 
MOESI_CMP_directory protocol?

Best regards

________________________________
Lu Zeng

Institute of Computing Technology,
Chinese Academy of Science

From: [email protected]<mailto:[email protected]>
Date: 2013-11-06 15:19
To: gem5 users mailing list<mailto:[email protected]>
Subject: [gem5-users] ruby MOESI_CMP_directory Invalid RubyRequestType
Hi, everyone,

I'm using ruby runing parsec blackscholes. After a long time run, it reports 
panic as follows:

panic: Runtime Error at MOESI_CMP_directory-L1cache.sm:243, Ruby Time: 
6092631646, Invalid RubyRequestType.

My command is:

./build/ALPHA_MOESI_CMP_directory/gem5.opt ./configs/example/ruby_fs.py -n 4 
--script=./dist-parsec/genrcS/blackscholes_4c_simmedium_ckpts.rcS

and the termial output appears to be:

PARSEC Benchmark Suite Version 2.1
[HOOKS] PARSEC Hooks Version 1.2
Num of Options: 16384
Num of Runs: 100
Size of data: 6

btw: there is no modification of the code

best regards

________________________________
Lu Zeng

Institute of Computing Technology,
Chinese Academy of Science
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to