On 20/06/14 11:25, James Hogan wrote: > From: Sanjay Lal <sanj...@kymasys.com> > > Add VMStateDescription for GT64120 PCI emulation used by the Malta > platform, to allow it to work with savevm/loadvm and live migration. > > The entire register array is saved/restored using VMSTATE_UINT32_ARRAY > (fixed length GT_REGS = 1024). > > Signed-off-by: Sanjay Lal <sanj...@kymasys.com> > [james.ho...@imgtec.com: Convert to VMState] > Signed-off-by: James Hogan <james.ho...@imgtec.com> > Cc: Aurelien Jarno <aurel...@aurel32.net> > --- > This is based on "[Patch 03/12] KVM/MIPS: Add save/restore state APIs > for saving/restoring KVM guests."[1]. > > Changes in v3: > - Save entire register array using VMSTATE_UINT32_ARRAY (which is fixed > length of GT_REGS = 1024) rather than individual registers. This is > safer in case an important register is missed or new emulated > functionality is added. (Aurelien Jarno)
For the record, Aurelien's question about saving all registers or only specific ones is still open (I also don't have enough experience to be sure, although I prefer the approach in v3). On 19/06/14 16:51, Aurelien Jarno wrote: > That said there might be some drawbacks in doing that, and I don't > really have enough experience to judge about that. It would be nice if > some more people can give their opinion there. Note, new emulated functionality may still require VMState versioning to handle unexpected zero register values in restored state. Cheers James
