qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: patches@linaro.org, "Paul Burton" <paul.burton@mips.com>,
	"Aurelien Jarno" <aurelien@aurel32.net>,
	"Yongbok Kim" <yongbok.kim@mips.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	"Juan Quintela" <quintela@redhat.com>,
	dgilbert@redhat.com
Subject: [Qemu-devel] [PATCH 1/2] hw/mips/boston: don't make flash region 'nomigrate'
Date: Mon,  4 Jun 2018 12:03:57 +0100	[thread overview]
Message-ID: <20180604110358.2821-2-peter.maydell@linaro.org> (raw)
In-Reply-To: <20180604110358.2821-1-peter.maydell@linaro.org>

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>
---
 hw/mips/boston.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/hw/mips/boston.c b/hw/mips/boston.c
index 5302e5c885..1d136529ad 100644
--- a/hw/mips/boston.c
+++ b/hw/mips/boston.c
@@ -471,8 +471,7 @@ static void boston_mach_init(MachineState *machine)
     sysbus_mmio_map_overlap(SYS_BUS_DEVICE(s->cps), 0, 0, 1);
 
     flash =  g_new(MemoryRegion, 1);
-    memory_region_init_rom_nomigrate(flash, NULL,
-                                     "boston.flash", 128 * M_BYTE, &err);
+    memory_region_init_rom(flash, NULL, "boston.flash", 128 * M_BYTE, &err);
     memory_region_add_subregion_overlap(sys_mem, 0x18000000, flash, 0);
 
     ddr = g_new(MemoryRegion, 1);
-- 
2.17.1

  reply	other threads:[~2018-06-04 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 11:03 [Qemu-devel] [PATCH 0/2] mips boston/malta: don't have nomigrate RAM regions Peter Maydell
2018-06-04 11:03 ` Peter Maydell [this message]
2018-06-04 13:21   ` [Qemu-devel] [PATCH 1/2] hw/mips/boston: don't make flash region 'nomigrate' Cédric Le Goater
2018-06-04 14:02   ` Philippe Mathieu-Daudé
2018-06-04 11:03 ` [Qemu-devel] [PATCH 2/2] hw/mips/mips_malta: don't make bios " Peter Maydell
2018-06-04 13:21   ` Cédric Le Goater
2018-06-04 14:02   ` Philippe Mathieu-Daudé
2018-06-15 10:08 ` [Qemu-devel] [PATCH 0/2] mips boston/malta: don't have nomigrate RAM regions Peter Maydell
2018-06-15 17:14   ` Paul Burton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180604110358.2821-2-peter.maydell@linaro.org \
    --to=peter.maydell@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=clg@kaod.org \
    --cc=dgilbert@redhat.com \
    --cc=patches@linaro.org \
    --cc=paul.burton@mips.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=yongbok.kim@mips.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).