----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/9/#review12 -----------------------------------------------------------
Ship it! I'm guessing this leads to confusing error messages when the object doesn't have a 'clock' param, but that's not easily fixable. - Steve On 2010-04-18 22:45:48, Nathan Binkert wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.m5sim.org/r/9/ > ----------------------------------------------------------- > > (Updated 2010-04-18 22:45:48) > > > Review request for Default. > > > Summary > ------- > > params: add a mechanism to the config system to specify cycles > Latencies can be specified as '2ns' or '1t' meaning 2 nanoseconds and > one "tick" respectively. This patch adds '1c' which means 1 cycle. > The cycle is the clock cycle of the current object, so the current > object must have an object called clock that is a parameter of type > Clock. Literally, '1c' means 1 * Self.clock.latency, so it's not > strictly necessary, but it sure is handy. > > > Diffs > ----- > > src/python/m5/params.py edde97a6ea7c > > Diff: http://reviews.m5sim.org/r/9/diff > > > Testing > ------- > > > Thanks, > > Nathan > > _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
