Hi Nilay, I saw the e-mail, I am just not sure what it is you want me to change. The clock is already set in configs/ruby/Ruby.py.
Is there any particular part of the patch that should change, if so which one? RB is probably the easiest way to capture this. Thanks, Andreas On 12/06/2013 12:57, "Nilay Vaish" <[email protected]> wrote: >Andreas, did you miss this email? > >---------- Forwarded message ---------- >Date: Thu, 6 Jun 2013 09:36:28 >From: Nilay Vaish <[email protected]> >To: Andreas Hansson <[email protected]> >Cc: Default <[email protected]> >Subject: Re: Review Request: config: Rename clock option to Ruby clock > >On Thu, 6 Jun 2013, Andreas Hansson wrote: > >> >> >>> On June 1, 2013, 9:33 a.m., Nilay Vaish wrote: >>>> I think there is no need for this ruby clock. Just set it to cpu >>>>clock. >>> >>> Andreas Hansson wrote: >>> Really? I am not sure what the Ruby clock corresponds to in a real >>> system, but if it is interconnect + L2 caches (and beyond) then surely >>>it >>> should not be the CPU clock? > >Ruby includes the entire memory system. > >>> >>> Perhaps I'm missing something about how Ruby treats the clock. >> >> Do we need a more in-depth discussion of what clock domains there >>should be >> in a Ruby "system" and what their counterpart is in a real system? >> > >You can leave that Ruby clock in there if you like. Just move it to the >file >configs/ruby/Ruby.py. > >-- >Nilay > -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
