This doesn't guarantee it too because there is a chance that you will create the checkpoint before the thread creation . If you want to make sure the checkpoint happen after all the randomness in the program you have to hack the benchmark to create the checkpoint at the point you want
On Tue, Sep 27, 2011 at 10:23 AM, sparsh mittal <[email protected]> wrote: > Hello > This refers to a previous reply of Avadh: >> >> To run simulations in more deterministic way, first create all the >> processes, threads and assign them on your desired CPU. Then create a >> checkpoint so when you run your simulation, it will not run any OS level >> task scheduling (unless something new comes up..). I use this method to run >> simulations in more deterministic way. To synchronize across multiple >> processes, you can use named semaphores to sync them. > > I wanted to ask if you could give an example. I tried the following but it > does not work. > taskset ... parsecmgmt ...b1 & taskset ... parsecmgmt ...b2; > ./create_checkpoint 2core_checkpoint; ./stop_sim > > Actually without deterministic simulation, I cannot verify/conclude anything > from the simulations. > Thanks and Regards > Sparsh Mittal > > > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > > _______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
