From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
lersek@redhat.com, kraxel@redhat.com,
Anthony Liguori <anthony@codemonkey.ws>,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] future proof rom loading for cross versiom migration
Date: Sun, 18 Aug 2013 16:41:13 +0300 [thread overview]
Message-ID: <20130818134113.GA5129@redhat.com> (raw)
In-Reply-To: <1376347400-21035-1-git-send-email-mst@redhat.com>
On Tue, Aug 13, 2013 at 01:43:29AM +0300, Michael S. Tsirkin wrote:
> Changes from v2: address comments on v2 by Peter Maydell
> - switch from global constant to function
> - use memory_region_init_ram instead of _ram_ptr
> - disable for 1.6
>
> Changes from v1: address comments by Peter Maydell
> - drop useless data=data line
> - rename target_page_size to migration_page_size to make use clear
> Peter, you also suggested somehow hiding this within memory core.
> I don't see a clean way to do this without lots of code
> changes, I think what I propose here is acceptable for now
> and we can always rework APIs without wire format changes.
>
> Please review, and consider for merging.
Ping. Any more comments?
Also - which tree can this go in through?
Mine?
> Original cover letter below.
>
>
> ROM files that are put in FW CFG are copied to guest ram, by BIOS, but
> they are not backed by RAM so they don't get migrated.
>
> Each time we'll change at least two bytes in such a ROM this will break
> cross-version migration: since we can migrate after BIOS has read the first
> byte but before it has read the second one, getting an inconsistent state.
>
> This patchset makes QEMU future-proof against such changes.
>
> Naturally, this only helps for -M 1.6 and up, older machine types
> will still have the cross-version migration bug.
>
> I think this should be applied for 1.6, this way we won't
> have this problem from 1.7 and on.
>
> Michael S. Tsirkin (2):
> memory: export migration page size
> loader: put FW CFG ROM files into RAM
>
> arch_init.c | 6 ++++++
> hw/core/loader.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++---
> hw/i386/pc_piix.c | 2 ++
> hw/i386/pc_q35.c | 2 ++
> include/exec/memory.h | 1 +
> include/hw/loader.h | 1 +
> 6 files changed, 63 insertions(+), 3 deletions(-)
>
> --
> MST
>
next prev parent reply other threads:[~2013-08-18 13:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 22:43 [Qemu-devel] [PATCH v3 0/2] future proof rom loading for cross versiom migration Michael S. Tsirkin
2013-08-12 22:43 ` [Qemu-devel] [PATCH v3 1/2] memory: export migration page size Michael S. Tsirkin
2013-08-19 9:59 ` Laszlo Ersek
2013-08-19 10:21 ` Peter Maydell
2013-08-19 11:09 ` Laszlo Ersek
2013-08-19 11:18 ` Michael S. Tsirkin
2013-08-19 11:33 ` Laszlo Ersek
2013-08-19 11:05 ` Michael S. Tsirkin
2013-08-12 22:43 ` [Qemu-devel] [PATCH v3 2/2] loader: put FW CFG ROM files into RAM Michael S. Tsirkin
2013-08-19 11:06 ` Laszlo Ersek
2013-08-19 11:10 ` Michael S. Tsirkin
2013-08-19 11:15 ` Laszlo Ersek
2013-08-19 11:21 ` Michael S. Tsirkin
2013-08-18 13:41 ` Michael S. Tsirkin [this message]
2013-08-19 11:37 ` [Qemu-devel] [PATCH v3 0/2] future proof rom loading for cross versiom migration Laszlo Ersek
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=20130818134113.GA5129@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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).