Hi Nilay, I¹m not really sure what you are suggesting. How could MemConfig solve this? My gut feeling is that the AbstractMemory (and all classes inheriting from it) needs to support multiple ranges.
If we ignore the KVM CPU then the AddrMapper would suffice. Andreas On 21/01/2014 18:58, "Nilay Vaish" <[email protected]> wrote: >On Tue, 21 Jan 2014, Andreas Hansson wrote: > >> >> ----------------------------------------------------------- >> This is an automatically generated e-mail. To reply, visit: >> http://reviews.gem5.org/r/2148/#review4875 >> ----------------------------------------------------------- >> >> >> It looks much better with the comments. >> >> One potential concern is that we consider each memory range as a >> separate multi-channel DRAM controller. Hence, when we split 4 GB into >>3 >> GB + 1 GB, we now create a (potentially multi-channel) controller per >> range. If the user says 4 channel DDR3, we now have 8 channels of DDR3. >> >> I don't know what is sensible to do here, but perhaps this solutions >> needs to be a bit more elaborate, and involve an AddrMapper one way or >> another? >> > >I think this a short coming of the mem_config() function. > >-- >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. 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
