----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/1891/#review4380 -----------------------------------------------------------
Ship it! Ship It! - Ali Saidi On June 3, 2013, 5:35 a.m., Andreas Sandberg wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1891/ > ----------------------------------------------------------- > > (Updated June 3, 2013, 5:35 a.m.) > > > Review request for Default. > > > Description > ------- > > Changeset 9741:a2b7eb136cea > --------------------------- > cpu: Add support for scheduling multiple inst/load stop events > > Currently, the only way to get a CPU to stop after a fixed number of > instructions/loads is to set a property on the CPU that causes a > SimLoopExitEvent to be scheduled when the CPU is constructed. This is > clearly not ideal in cases where the simulation script wants the CPU > to stop at multiple instruction counts (e.g., SimPoint generation). > > This changeset adds the methods scheduleInstStop() and > scheduleLoadStop() to the BaseCPU. These methods are exported to > Python and are designed to be used from the simulation script. By > using these methods instead of the old properties, a simulation script > can schedule a stop at any point during simulation or schedule > multiple stops. The number of instructions specified when scheduling a > stop is relative to the current point of execution. > > > Diffs > ----- > > src/cpu/BaseCPU.py 304a37519d11 > src/cpu/base.hh 304a37519d11 > src/cpu/base.cc 304a37519d11 > > Diff: http://reviews.gem5.org/r/1891/diff/ > > > Testing > ------- > > > Thanks, > > Andreas Sandberg > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
