[gem5-dev] changeset in gem5: kvm: Add checkpoint debug print

[Andreas Sandberg]

changeset 2c52e4537e6c in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=2c52e4537e6c
description:
        kvm: Add checkpoint debug print

        Add a debug print (when the Checkpoint debug flag is set) on serialize
        and unserialize. Additionally, dump the KVM state before
        serializing. The KVM state isn't dumped after unserializing since the
        state is loaded lazily on the next KVM entry.

diffstat:

 src/cpu/kvm/base.cc |  8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diffs (32 lines):

diff -r c4d3b62b3fcf -r 2c52e4537e6c src/cpu/kvm/base.cc
--- a/src/cpu/kvm/base.cc       Thu May 02 12:01:50 2013 +0200
+++ b/src/cpu/kvm/base.cc       Thu May 02 12:02:19 2013 +0200
@@ -48,6 +48,7 @@
 
 #include "arch/utility.hh"
 #include "cpu/kvm/base.hh"
+#include "debug/Checkpoint.hh"
 #include "debug/Kvm.hh"
 #include "debug/KvmIO.hh"
 #include "debug/KvmRun.hh"
@@ -213,6 +214,11 @@
 void
 BaseKvmCPU::serializeThread(std::ostream &os, ThreadID tid)
 {
+    if (DTRACE(Checkpoint)) {
+        DPRINTF(Checkpoint, "KVM: Serializing thread %i:\n", tid);
+        dump();
+    }
+
     // Update the thread context so we have something to serialize.
     syncThreadContext();
 
@@ -225,6 +231,8 @@
 BaseKvmCPU::unserializeThread(Checkpoint *cp, const std::string &section,
                               ThreadID tid)
 {
+    DPRINTF(Checkpoint, "KVM: Unserialize thread %i:\n", tid);
+
     assert(tid == 0);
     assert(_status == Idle);
     thread->unserialize(cp, section);
_______________________________________________
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev