The main reason not to delete the old config files now is libruby has yet to be updated. I wanted to hear Derek and others opinion before I removed the files.
Brad > -----Original Message----- > From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On > Behalf Of nathan binkert > Sent: Friday, January 15, 2010 11:52 AM > To: M5 Developer List > Subject: Re: [m5-dev] [PATCH 00 of 41] Ruby Config Updated Patches > > > - These patches do not remove the old ruby config and rubymem files. > However, once these patches are checked in, those old files won't be > needed. Anyone have an opinion on how long they would like those files > to stick around? I would like to delete them as soon as we can. > > Why not delete them now? > > > - There are a few places where the block offset (i.e. the > l2_select_low_bit) is defaulted to 6 assuming 64-byte cache blocks. I > would like to instead take the log2 of RubySystem's block_size_bytes > parameter, however the following code will not work: > > l2_select_low_bit = Param.Int(math.log((Param.RubySystem(Parent.any, > "block offset")).block_size_bytes, 2), "") > > I would be interested to hear any suggestions people have to make > something like this work. > > Param.foo is not a value, so you can't do stuff like this to it. > Parent.any is a proxy class and we've defined some mathematical > operations for it. We could consider defining others. Alternatively, > we could try to support some sort of method invocation as a value. > > > Nate > _______________________________________________ > m5-dev mailing list > m5-dev@m5sim.org > http://m5sim.org/mailman/listinfo/m5-dev _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
