----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/57/#review97 -----------------------------------------------------------
configs/common/Options.py <http://reviews.m5sim.org/r/57/#comment241> You don't have to change this if you don't feel like it, but the dest="" thing isn't necessary. --smarts-sample-interval becomes options.smarts_sample_interval. I prefer that they're consistent myself. The only real reason (I think) to use dest= is if you have multiple options that affect the same variable. - Nathan On 2010-07-16 18:22:50, Timothy Jones wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.m5sim.org/r/57/ > ----------------------------------------------------------- > > (Updated 2010-07-16 18:22:50) > > > Review request for Default. > > > Summary > ------- > > Sim: Add functionality to the simulation scripts to allow running with > SMARTS sampling methodology. At the moment the scripts don't support the > full range of options (e.g. you can't start from a checkpoint), and nor do > they check for incompatibility with other options. However, they do give > an example of how sampling could work with M5. > > With a benchmark that has 10 billion dynamic instructions, try: > > <m5bin> configs/example/se.py -d --caches --smarts:n 10000 --smarts:b 10 > > > Diffs > ----- > > configs/common/Options.py 249f174e6f37 > configs/common/Simulation.py 249f174e6f37 > configs/common/Smarts.py PRE-CREATION > > Diff: http://reviews.m5sim.org/r/57/diff > > > Testing > ------- > > > Thanks, > > Timothy > > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
