Hi All,
These two days I try to run parsec in Alpha FS mode with ruby (use MOESI_hammer 
protocol). After attempted with several combinations in the simulation, I found 
such situation: 
Without ruby attached (i.e., fs.py is used), I can successfully run parsec with 
and without the checkpoint. However, with ruby attached (i.e., ruby_fs.py is 
used), different combinations used in the simulation got different results as 
below:
1. cpu-type=timing, checkpoint disabled, simulation result: succeed;
2. cpu-type=timing, checkpoint enabled, simulation result: failed;
3. cpu-type=detailed, checkpoint enabled or disabled, simulation result: 
failed. 
In these simulations, only situation 1 succeed on the condition that "swithcpu" 
should be disabled. Each time I switched cpu type from timing to detailed, the 
program aborts.  As for situations 2 and 3, they always abort with certain 
errors. I search the gem5 mail-list archive and found that Nilay and Yuan have 
pointed out "In essence, the checkpointing support was added to Ruby with the 
assumption that simulation would stop after the checkpoint is created." 
However, the problem remains unsolved.
In summary, has anyone successfully run parsec in Alpha FS mode with ruby and 
checkpoint? Would you please share your experience with me? Thank you very much!

Best regards,
Song Jin

------------------------------------------------------------------------
Song Jin, Ph. D.
Department of Electronic and Communication Engineering 
School of Electrical and Electronic Engineering 
North China Electric Power University, P. R. China
Web: http://www.ncepu.edu.cn
------------------------------------------------------------------------
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to