I am ready to change abstract memory, but first I want to get those ruby
port patches done and dusted.
--
Nilay
On Wed, 22 Jan 2014, Andreas Hansson wrote:
Hi Nilay,
If it¹s urgent, then go ahead, although I think it opens up for some
confusion about what system is really being simulated. If possible, I¹d
suggest to first add the support in the memory classes though, and push
that before the current patch goes in.
Andreas
On 22/01/2014 13:02, "Nilay Vaish" <[email protected]> wrote:
On Wed, 22 Jan 2014, Andreas Hansson wrote:
Hi Nilay,
I¹d rather phrase it as: What needs to be done to support multiple
(non-contiguous) memory ranges? Your patch solves part of the problem,
and
also exposes the need for some further changes. I¹m merely keen to pin
point what needs to be done, and then divvy up the work one way or
another.
I take that as you are fine with the patch being committed. And I agree
with you that AbstractMemory class needs to support multiple address
ranges, at least for x86. I don't know whether other ISAs have similar
holes in the address range.
--
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
