gem5/configs/ruby
Andreas Hansson a128ba7cd1 Ruby: Remove the physMemPort and instead access memory directly
This patch removes the physMemPort from the RubySequencer and instead
uses the system pointer to access the physmem. The system already
keeps track of the physmem and the valid memory address ranges, and
with this patch we merely make use of that existing functionality. The
memory is modified so that it is possible to call the access functions
(atomic and functional) without going through the port, and the memory
is allowed to be unconnected, i.e. have no ports (since Ruby does not
attach it like the conventional memory system).
2012-03-30 09:42:36 -04:00
..
MESI_CMP_directory.py Ruby: Remove the physMemPort and instead access memory directly 2012-03-30 09:42:36 -04:00
MI_example.py Ruby: Remove the physMemPort and instead access memory directly 2012-03-30 09:42:36 -04:00
MOESI_CMP_directory.py Ruby: Remove the physMemPort and instead access memory directly 2012-03-30 09:42:36 -04:00
MOESI_CMP_token.py Ruby: Remove the physMemPort and instead access memory directly 2012-03-30 09:42:36 -04:00
MOESI_hammer.py Ruby: Remove the physMemPort and instead access memory directly 2012-03-30 09:42:36 -04:00
Network_test.py Ruby: Remove the physMemPort and instead access memory directly 2012-03-30 09:42:36 -04:00
Ruby.py Ruby: Remove the physMemPort and instead access memory directly 2012-03-30 09:42:36 -04:00