Daniel P. Berrange 2594f56d4c migration: don't use an array for storing migrate parameters ... The MigrateState struct uses an array for storing migration parameters. This presumes that all future parameters will be integers too, which is not going to be the case. There is no functional reason why an array is used, if anything it makes the code less clear. The QAPI schema already defines a struct - MigrationParameters - capable of storing all the individual parameters, so just use that instead of an array. Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com> Message-Id: <1461751518-12128-25-git-send-email-berrange@redhat.com> Signed-off-by: Amit Shah <amit.shah@redhat.com>		2016-05-26 11:32:07 +05:30
..
block.h	migration: move include files to include/migration/	2012-12-19 08:31:32 +01:00
cpu.h	hw: move CPU state serialization to migration/cpu.h	2016-05-19 16:42:28 +02:00
migration.h	migration: don't use an array for storing migrate parameters	2016-05-26 11:32:07 +05:30
page_cache.h	xbzrle: optimize XBZRLE to decrease the cache misses	2015-01-15 17:49:43 +05:30
postcopy-ram.h	Postcopy: Mark nohugepage before discard	2015-11-10 15:00:28 +01:00
qemu-file.h	migration: delete QEMUFile stdio implementation	2016-05-26 11:32:03 +05:30
qjson.h	migration/qjson: Drop gratuitous use of QOM	2016-05-23 14:16:12 +05:30
vmstate.h	migration: Move qjson.[ch] to migration/	2016-05-23 14:16:09 +05:30