From d9fa950396e8f331bbfb1023348c8c680967b1be Mon Sep 17 00:00:00 2001 From: Marco Elver Date: Sat, 19 Apr 2014 09:00:30 -0500 Subject: ruby: recorder: Fix (de-)serializing with different cache block-sizes Upon aggregating records, serialize system's cache-block size, as the cache-block size can be different when restoring from a checkpoint. This way, we can correctly read all records when restoring from a checkpoints, even if the cache-block size is different. Note, that it is only possible to restore from a checkpoint if the desired cache-block size is smaller or equal to the cache-block size when the checkpoint was taken; we can split one larger request into multiple small ones, but it is not reliable to do the opposite. Committed by: Nilay Vaish --- src/sim/serialize.hh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/sim/serialize.hh') diff --git a/src/sim/serialize.hh b/src/sim/serialize.hh index bbf759cf6..5fc9d7b55 100644 --- a/src/sim/serialize.hh +++ b/src/sim/serialize.hh @@ -58,7 +58,7 @@ class EventQueue; * SimObject shouldn't cause the version number to increase, only changes to * existing objects such as serializing/unserializing more state, changing sizes * of serialized arrays, etc. */ -static const uint64_t gem5CheckpointVersion = 0x0000000000000009; +static const uint64_t gem5CheckpointVersion = 0x000000000000000a; template void paramOut(std::ostream &os, const std::string &name, const T ¶m); -- cgit v1.2.3