hw/mips/boston: don't make flash region 'nomigrate'
commit9581eeebe3ffd37f7fde270f92c96a2c5ebb860c
authorPeter Maydell <peter.maydell@linaro.org>
Mon, 4 Jun 2018 11:03:57 +0000 (4 12:03 +0100)
committerAleksandar Markovic <amarkovic@wavecomp.com>
Wed, 27 Jun 2018 18:10:54 +0000 (27 20:10 +0200)
tree9bb9f52de1559e8ad6b728ae03f65b04ccb18fce
parentc92023bfd18c968d615b715522467f7354db5877
hw/mips/boston: don't make flash region 'nomigrate'

Currently we use memory_region_init_rom_nomigrate() to create
the "boston.flash" memory region, and we don't manually register
it with vmstate_register_ram(). This currently means that its
contents are migrated but as a ram block whose name is the empty
string; in future it may mean they are not migrated at all. Use
memory_region_init_ram() instead.

Note that this is a a cross-version migration compatibility break
for the "boston" machine.

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Paul Burton <paul.burton@mips.com>
Signed-off-by: Aleksandar Markovic <aleksandar.markovic@mips.com>
hw/mips/boston.c