A couple of questions that I have been thinking about --
1. I went through the code for TraceRecord. When a RubyRequest is created using a trace record, the pkt pointer is provided as NULL. It seems to me that this would lead to something wrong later on when callback takes place. In particular, RubyPort::ruby_hit_callback() works on the packet pointer provided in a ruby request. I think TraceRecord is currently broken. It might be that patch you use for cache warmup makes changes to TraceRecord that make it work correctly. Is this true or am I reading the code incorrectly?
2. I went back and read the discussion on cache warmup that took place in late June. I am wondering about the need for timing cache warmup. Is it not possible to simply serialize the state of cache controller like it is done for other components of gem5?
Thanks Nilay _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
