Brad, but flushing the caches would mean that we cannot support periodic
checkpointing.
--
Nilay
On Wed, 7 Dec 2011, Beckmann, Brad wrote:
Switching to email.
The thing to remember is the cache trace doesn???t keep track of whether
shared data is dirty or not. It simply marks that address for a load
request. We don???t want to store dirty state in the cache since we
want to make these traces protocol agnostic and each protocol can
potentially manage dirty data differently. That is why the current
patch breaks those checks.
Brad
Brad, thanks for the review. I can take care of all of the things you have
pointed
out. I'll add functions for serializing and unserializing the memory image.
But I have other questions. Is flushing the cache necessary? If we are correctly
restoring the data in the caches, I think that we can checkpoint the memory
image even with stale data. Secondly, why were those checks breaking earlier?
I picked those lines directly from the patch you had provided to Somayeh.
- Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
