> Perhaps I am missing something, but why not simply remove the > serialize/unserialize and fall back on the empty default implementation? >
When I use the default implementation, the object name header is still serialized to the checkpoint - nameOut() is called before serialize() is called on the object in the static function SimObject::serializeAll(). This nameOut() function dumps a name header for each object to the checkpoint that are unnecessary for my purposes, so I was just wondering if there might be an easy way to keep this from happening. It doesn't appear that there's an easy way to do this without changing the nameOut() function to being virtual, or making tweaks to the way that SimObject::serializeAll() dumps to the checkpoint file. Joel > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Joel Hestness > Sent: 13 September 2012 06:00 > To: gem5 Developer List > Subject: [gem5-dev] Keep a MemObject from Being Serialized? > > Hey guys, > This is more of a nice-to-have than a need-to-have: Is there a way to > keep a MemObject (or any SimObject for that matter) from serializing to the > checkpoint file when checkpointing? I've got an object that I'm changing > either the quantity or type of when restoring from a checkpoint, and since > the checkpoint doesn't hold any state for these objects, it would be nice > to keep the checkpoint free of their clutter. > > Thanks, > Joel > > -- > Joel Hestness > PhD Student, Computer Architecture > Dept. of Computer Science, University of Wisconsin - Madison > http://www.cs.utexas.edu/~hestness > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev > -- Joel Hestness PhD Student, Computer Architecture Dept. of Computer Science, University of Wisconsin - Madison http://www.cs.utexas.edu/~hestness _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
