From: Juan Quintela <quintela@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] fdc: Fix vmsave/restore regression
Date: Thu, 12 Nov 2009 00:28:01 +0100 [thread overview]
Message-ID: <m38wecd4la.fsf@neno.mitica> (raw)
In-Reply-To: <4AFB4059.8020607@web.de> (Jan Kiszka's message of "Wed, 11 Nov 2009 23:53:13 +0100")
Jan Kiszka <jan.kiszka@web.de> wrote:
> This partly reverts 2be3783328: First, the conversion neglected to
> update the opaque translation in fdc_pre_save/fdc_post_load which causes
> memory corruptions on vmsave/restore. And second, we can't apply a
> common translation here as DeviceState->fdctrl_t is different for sysbus
> and ISA.
I finished today the proper patch. Please don't apply this one.
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> hw/fdc.c | 5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
> *** NOTE ***
> 'git shortlog|grep "reset + vmsd"' shows 10 such conversions. I only
> briefly checked the first one, and it looks similar broken. Could
> someone have a second look at them? Maybe it is also better to define a
> vmsd opaque in DeviceInfo, which would also allow to solve this issue
> differently.
It looks like a plan.
I am in the middle of trying to get migration working, and have at least
another 2 patches (appart from the one already in staging).
I am in the last round of testing.
Later, Juan.
next prev parent reply other threads:[~2009-11-11 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 22:53 [Qemu-devel] [PATCH] fdc: Fix vmsave/restore regression Jan Kiszka
2009-11-11 23:28 ` Juan Quintela [this message]
2009-11-12 13:00 ` [Qemu-devel] " Juan Quintela
2009-11-12 13:13 ` Jan Kiszka
2009-11-12 14:37 ` Juan Quintela
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=m38wecd4la.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@web.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.