On Sat, 6 Aug 2011, Carole-Jean Wu wrote:
Hi,
I am studying the interaction between user-mode and system-mode memory
reference using gem5. I am finding that all references are passed in as
supervisor mode references in system/RubyPort.cc recv_timing.
As a result, the information of RubyAccessMode is loss after the request
leaves processor issue engine.
Does anyone know how to appropriate set the RubyAccessMode in RubyPort.cc to
make this field hold valid information?
RubyRequest is created using a packet, so the packet should have the
information on the mode of the processor. I do not know if it has the
info, but if this info exists with the processor that generated the
packet, then it is easy to pass it in the packet.
--
Nilay
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
