From: mdroth <mdroth@linux.vnet.ibm.com>
To: qemu-trivial@nongnu.org
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
qemu-stable@nongnu.org, nick@bytemark.co.uk
Subject: Re: [Qemu-devel] [PATCH] wdt_i6300esb: fix vmstate versioning
Date: Wed, 12 Jun 2013 15:11:51 -0500 [thread overview]
Message-ID: <20130612201151.GF12585@vm> (raw)
In-Reply-To: <1369175577-18130-1-git-send-email-mdroth@linux.vnet.ibm.com>
On Tue, May 21, 2013 at 05:32:57PM -0500, Michael Roth wrote:
> When this VMSD was introduced it's version fields were set to
> sizeof(I6300State), making them essentially random from build to build,
> version to version.
>
> To fix this, we lock in a high version id and low minimum version id to
> support old->new migration from all prior versions of this device's
> state. This should work since the device state has not changed since
> its introduction.
>
> The potentially breaks migration from 1.5+ to 1.5, but since the
> versioning was essentially random prior to this patch, new->old
> migration was not consistently functional to begin with.
>
> Reported-by: Nicholas Thomas <nick@bytemark.co.uk>
> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
CC'ing qemu-trivial. Looking to get this in for 1.5.1
> ---
> hw/watchdog/wdt_i6300esb.c | 19 ++++++++++++++++---
> 1 file changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/hw/watchdog/wdt_i6300esb.c b/hw/watchdog/wdt_i6300esb.c
> index 1407fba..851b664 100644
> --- a/hw/watchdog/wdt_i6300esb.c
> +++ b/hw/watchdog/wdt_i6300esb.c
> @@ -374,9 +374,22 @@ static const MemoryRegionOps i6300esb_ops = {
>
> static const VMStateDescription vmstate_i6300esb = {
> .name = "i6300esb_wdt",
> - .version_id = sizeof(I6300State),
> - .minimum_version_id = sizeof(I6300State),
> - .minimum_version_id_old = sizeof(I6300State),
> + /* With this VMSD's introduction, version_id/minimum_version_id were
> + * erroneously set to sizeof(I6300State), causing a somewhat random
> + * version_id to be set for every build. This eventually broke
> + * migration.
> + *
> + * To correct this without breaking old->new migration for older versions
> + * of QEMU, we've set version_id to a value high enough to exceed all past
> + * values of sizeof(I6300State) across various build environments, and have
> + * reset minimum_version_id_old/minimum_version_id to 1, since this VMSD
> + * has never changed and thus can except all past versions.
> + *
> + * For future changes we can treat these values as we normally would.
> + */
> + .version_id = 10000,
> + .minimum_version_id = 1,
> + .minimum_version_id_old = 1,
> .fields = (VMStateField []) {
> VMSTATE_PCI_DEVICE(dev, I6300State),
> VMSTATE_INT32(reboot_enabled, I6300State),
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2013-06-12 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 22:32 [Qemu-devel] [PATCH] wdt_i6300esb: fix vmstate versioning Michael Roth
2013-05-22 8:25 ` Laszlo Ersek
2013-05-23 11:19 ` Amit Shah
2013-06-12 20:11 ` mdroth [this message]
2013-06-12 20:42 ` Peter Maydell
2013-06-12 21:07 ` mdroth
2013-06-12 21:17 ` Anthony Liguori
2013-06-12 21:27 ` mdroth
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=20130612201151.GF12585@vm \
--to=mdroth@linux.vnet.ibm.com \
--cc=nick@bytemark.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).