Hi, You are right but the problem is I have set some meanningful names to the checkpoint files. For example I have these workloads: /home/mahmood/workloads/work1-small-cold-1core /home/mahmood/workloads/work1-small-cold-4core /home/mahmood/workloads/work1-large-cold-1core /home/mahmood/workloads/work1-large-cold-4core
/home/mahmood/workloads/work2-small-cold-1core /home/mahmood/workloads/work2-small-cold-4core /home/mahmood/workloads/work2-large-cold-1core /home/mahmood/workloads/work2-large-cold-4core I had created them before. Now if phase_000 is hard coded then I have to open all checkpoint files and rename the file namaes or I have to recreate checkpoints with a new file name (all of them are phase_000). Is there any shortcut? // Naderan *Mahmood; ________________________________ From: Volos Stavros <[email protected]> To: Mahmood Naderan <[email protected]> Sent: Sat, June 26, 2010 12:22:00 AM Subject: Re: Changing checkpoint name in "job-load.simics" Hi Mahmood, Why do you want to change the checkpoint file name in this file? This is a file that is related to what you are running. For example if you try to run the workload TEST_APP for the phase_000 the corresponding job file will have the phase_000 checkpoint. If you want to run a different workload you should define it in the .run_job.rc.tcl file. Regards, -Stavros On Jun 25, 2010, at 12:28 PM, Mahmood Naderan wrote: Hi, >How can I change checkpoint file name in "job-load.simics" (flexus >4)? "run_job" >use that in the "start.simics" (run-command-file job-load.simics), but this >file >is a runtime file and reside in the result directory. > >// Naderan *Mahmood; > >
