3d2052bc03
With the introduction of multi-ISA gem5, we don't store the TARGET_ISA anymore as a string in the root section of the checkpoint [1]. There is therefore no way at the moment to asses the ISA of a CPU/ThreadContext. This is a problem when it comes to checkpoint updates which are ISA specific. By explicitly serializing the ISA as a string under the cpu.isa section we avoid this problem and we let cpt_upgraders be aware of the ISA in use. [1]: https://gem5-review.googlesource.com/c/public/gem5/+/48884 Signed-off-by: Giacomo Travaglini <giacomo.travaglini@arm.com> Change-Id: I1e75230cbc370cab84f4a54141b1e425af2dbfac Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com>