From: Marcelo Tosatti <mtosatti@redhat.com>
To: Philipp Hahn <hahn@univention.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 1/2] acpi_piix4: fix migration of gpe fields
Date: Mon, 20 Mar 2017 20:20:32 -0300 [thread overview]
Message-ID: <20170320232032.GA28018@amt.cnet> (raw)
In-Reply-To: <f8f0ebb7-0c79-8570-3210-dc45c3effda8@univention.de>
On Mon, Mar 20, 2017 at 01:02:10PM +0100, Philipp Hahn wrote:
> Hello Marcelo, cc:qemu,
>
> Sorry for re-using this old thread, but I have a problem loading some
> saved state from qemu-kvm-1.1.2, which fails for piix4_pm.
>
> You following patch was committed as
> <http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=b0b873a07872f7ab7f66f259c73fb9dd42aa66a9>:
>
> Am 15.11.2012 um 01:11 schrieb Marcelo Tosatti:
> > Migrate 16 bytes for en/sts fields (which is the correct size),
> > increase version to 3, and document how to support incoming
> > migration from qemu-kvm 1.2.
>
> I my case qemu-kvm-1.1.2/hw/acpi_piix4.c:284
> | VMSTATE_STRUCT(ar.gpe, PIIX4PMState, 2, vmstate_gpe, ACPIGPE),
> only saves 4 bytes, not 16 bytes.
Hi Philipp,
IIRC qemu-1.1.2 saved 16 bytes, which is the correct size, not 4 bytes.
So while merging from qemu-kvm -> qemu, it was decided to maintain
backwards compability with qemu, and not qemu-kvm.
Is there any way to differentiate between the two (qemu vs qemu-kvm,
perhaps via some other field not in the VMState of ACPI PIIX4), so
your patch can be integrated upstream?
next prev parent reply other threads:[~2017-03-20 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 0:11 [Qemu-devel] [PATCH 0/2] [PULL] qemu-kvm.git uq/master queue Marcelo Tosatti
2012-11-15 0:11 ` [Qemu-devel] [PATCH 1/2] acpi_piix4: fix migration of gpe fields Marcelo Tosatti
2017-03-20 12:02 ` Philipp Hahn
2017-03-20 23:20 ` Marcelo Tosatti [this message]
2017-03-21 9:03 ` Philipp Hahn
2012-11-15 0:11 ` [Qemu-devel] [PATCH 2/2] kvm: Actually remove software breakpoints from list on cleanup Marcelo Tosatti
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=20170320232032.GA28018@amt.cnet \
--to=mtosatti@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=hahn@univention.de \
--cc=kvm@vger.kernel.org \
--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 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).