Hi Daniel, Supporting old checkpoint is something nice but has the cost of having to update util/cpt_upgrader.py for every sensible addition. The end result as you are saying will be a gigantic, overpopulated cpt_upgrader patcher.
What about defining checkpoint history windows: we support restoring checkpoints only if they are not older than the time frame. In this way we can flush the cpt_upgrader at the end of each window (could it be something like 1 year time?) Let me know what do you think about this. regards Giacomo ________________________________ From: gem5-dev <[email protected]> on behalf of Daniel Carvalho <[email protected]> Sent: 20 February 2019 11:35 To: Gem5 Developer List Subject: [gem5-dev] Checkpoint upgrader Hello, all. Recently I discovered the util/cpt_upgrader.py, a tool that relies on the existence of upgraders, which should be added for every modification of checkpoints. Was it something that indeed worked? The last upgrader was added 2 years ago; is there a specific reason why support for what seems to be a very handy program has been dropped? One thing we could do to mitigate future lack of upgraders would be to create a verifier that warns the user when a SERIALIZE/UNSERIALIZE is added/removed, and a respective upgrader isn't added. This, however, will likely overpopulate the cpt_upgraders. Regards,Daniel _______________________________________________ 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
