I have noticed that many of the action definitions are missing
out_msg.RequestorMachine assignments and it causes m5 to die when run with
--trace-flags=RubyNetwork.  I have fixed it locally by setting the
RequestorMachine to L1Cache for each of these, but I don't know enough about
the codebase to know if that is a proper fix.

Is there a fix for this in the pipeline?

-Joseph
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to