ruby: single physical memory in fs mode
Review Request #2209 - Created March 12, 2014 and submitted
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 10497:79c54592d7c5 --------------------------- ruby: single physical memory in fs mode Both ruby and the system used to maintain memory copies. With the changes carried for programmed io accesses, only one single memory is required for fs simulations. This patch sets the copy of memory that used to reside with the system to null, so that no space is allocated, but address checks can still be carried out. All the memory accesses now source and sink values to the memory maintained by ruby.
I realise it is beyond this patch, but it would be very nice to see the memory controller broken out of Ruby. In other words, keep the directory controller, and use a "normal" gem5 port to interface to a subclass of AbstractMemory.
-
tests/configs/pc-simple-timing-ruby.py (Diff revision 1) -
Why is this needed?
Review request changed
Updated (Sept. 24, 2014, 9:41 p.m.)
Description: |
|
|||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+97 -116) |
Posted (Oct. 21, 2014, 5:03 a.m.)
Would be good to get this and the other Ruby/memory system interaction patches out there.
Review request changed
Updated (Oct. 21, 2014, 3 p.m.)
Description: |
|
|||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 3 (+90 -55) |
Review request changed
Updated (Oct. 23, 2014, 9:08 a.m.)
Summary: |
|
|||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: |
|
|||||||||||||||||||||||||||||||||||||||
Diff: |
Revision 4 (+90 -55) |