Hi everyone, I am merely curious to know if we can prune the RubyMemoryControl (I’d like to minimise the number of subclasses that need modifications as AbstractMemory changes). As you are probably aware, the DRAMCtrl class has a GDDR5 config (as well as LPDDRx, DDRx, WideIOx), and is completely integrated with DRAMPower. We are also about to push out some further patches adding low-power-state control to the DRAMCtrl. I would think DRAMCtrl Pareto dominates the RubyMemoryControl by far, but I could be missing something.
Thanks, Andreas -- 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. ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782 _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
