> On May 1, 2014, 11:05 p.m., Nilay Vaish wrote:
> > Why is the clock period associated with each clocked object not enough?

There is a difference between the controller clock (which is what the DRAMCtrl 
clock domain would currently communicate), and the DRAM clock (tCK in DRAM 
speak). The other option compared to what we have done in this patch is to add 
a DRAM SimObject and let the DRAMCtrl have a pointer to it. The DRAM object 
could then be placed in a DRAM clock domain with tCK as its clock. That seems 
awfully bulky though.


- Andreas


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2269/#review5066
-----------------------------------------------------------


On April 23, 2014, 12:37 p.m., Andreas Hansson wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/2269/
> -----------------------------------------------------------
> 
> (Updated April 23, 2014, 12:37 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> -------
> 
> Changeset 10221:02b6fdd33908
> ---------------------------
> mem: Add DRAM cycle time
> 
> This patch extends the current timing parameters with the DRAM cycle
> time. This is needed as the DRAMPower tool expects timestamps in DRAM
> cycles. At the moment we could get away with doing this in a
> post-processing step as the DRAMPower execution is separate from the
> simulation run. However, in the long run we want the tool to be called
> during the simulation, and then the cycle time is needed.
> 
> 
> Diffs
> -----
> 
>   src/mem/DRAMCtrl.py e40b35147270 
>   src/mem/dram_ctrl.hh e40b35147270 
>   src/mem/dram_ctrl.cc e40b35147270 
> 
> Diff: http://reviews.gem5.org/r/2269/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Andreas Hansson
> 
>

_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to