I was working on getting the X86_FS working with the timing simple CPU as well as it does with atomic, and found that when called in my page table walker, sys->getMemoryMode() is very definitely giving the wrong answer. I suspect there's something I didn't do quite right when setting up the system object, but since part of that is in python I wasn't sure how it all went together. Why might my system object think it's in atomic mode when it's actually in timing? How does it end up assuming one mode or the other?
Gabe _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
