hello, Korey thanks for your reply.
I have check the m5 cmd with help option, it does have two options to limit the max instructions, one is --maxinsts=MAXINSTS the other is -I MAX_INST, --max-inst=MAX_INST Total number of instructions to simulate (default: run forever) I'm a little confused which one to use. Also here is another question. Assume I set the max instruction is 1 billion when I restore from a checkpoint, such as ./build/ALPHA_FS/m5.opt ./configs/example/fs.py -n4 -d --caches --l2cache --maxinsts=1000000000 --checkpoint-restore=1 The 1 billion instruction limitation should not include the number of instruction executed when making the checkpoint. Is that right? E.g. When making the checkpoint, M5 have already run 100M instructions, then I input a cmd as shown before, run the max instructions limitation with 1 billion. When the M5 stops, the total amount of executed instruction by M5 should be 1.1 billion(1+0.1), not 1 billion. That means the limitation of 1 billion is all for the run after the checkpoint. Is that right? Many thanks again David On Fri, Feb 18, 2011 at 11:00 AM, <[email protected]> wrote: > Send m5-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of m5-users digest..." > > > Today's Topics: > > 1. Re: How to control max instructions for PARSEC after > restoring from ROI checkpoint (Korey Sewell) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 18 Feb 2011 10:20:18 -0500 > From: Korey Sewell <[email protected]> > To: M5 users mailing list <[email protected]> > Subject: Re: [m5-users] How to control max instructions for PARSEC > after restoring from ROI checkpoint > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Dave, > should it not be "--maxinsts" not "--max-inst"? Is that a typo in your > email > or sim script? > > On Fri, Feb 18, 2011 at 10:06 AM, Dawei Wang <[email protected] > >wrote: > > > Hello, everyone > > > > Recently I now using M5 and Parsec to do some experiments about caches. > But > > running full Parsec benchmark with simmedium and simlarge in detailed O3 > CPU > > mode takes too too long time. In my experience, X264, facesim, and > freqmine > > will be more than 1 week to simulate. So I have to limit the maximum > > instructions when M5 restore from ROI checkpoint. I did some experiments > > with M5 cmd, but it doesn't work. Here are the cmd line > > > > 1.first create ROI checkpoint > > ./build/ALPHA_FS/m5.opt ./configs/example/fs.py -n 4 > > --script=./parsec_script/bodytrack/bodytrack_4c_simmedium_ckpts.rcS > > > > 2.restore from ROI checkpoint, run extra 1 billion instructions for ROI > > part using --max-inst option. > > ./build/ALPHA_FS/m5.opt ./configs/example/fs.py -n 4 -d --caches > --l2cache > > --max-inst=1000000000 --checkpoint-restore=1 > > > > The simulation successfully running with detailed mode, but it does not > > stop after arrive at the 1 billion instruction, here are some results > shown > > in m5out/stats.txt. It seems the M5 already exceeded 1 billion > instruction > > limitation (In this results, m5 already run more than 3.8 billion > > instructions). So my question, how could I control max instruction for > > PARSEC after its restoring from ROI checkpoint? > > > > ---------- Begin Simulation Statistics ---------- > > host_inst_rate 142861 # Simulator instruction > > rate (inst/s) > > host_mem_usage 701880 # Number of bytes of host > memory > > used > > host_seconds 22973.84 # Real time elapsed on the > > host > > host_tick_rate 18711184 # Simulator tick rate > > (ticks/s) > > sim_freq 1000000000000 # Frequency of simulated > ticks > > sim_insts 3282054759 # Number of instructions > > simulated > > sim_seconds 0.429868 # Number of seconds > simulated > > sim_ticks 429867680500 # Number of ticks simulated > > > > > > Many thinks in advance. > > > > David > > > > > > > > > > > > _______________________________________________ > > m5-users mailing list > > [email protected] > > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > > > > > > -- > - Korey > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://m5sim.org/cgi-bin/mailman/private/m5-users/attachments/20110218/6150b2da/attachment-0001.html > > > > ------------------------------ > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > > End of m5-users Digest, Vol 55, Issue 37 > **************************************** >
_______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
