From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/9] Optional toplevel sections
Date: Thu, 14 May 2015 18:28:31 +0200 [thread overview]
Message-ID: <1431620920-19710-1-git-send-email-quintela@redhat.com> (raw)
Hi
[v2]
- Rebased to current tree
- Added global configuration section, not sent/received for previous
machine types.
Please, review.
Thanks, Juan.
[v1]
by popular demand, and after too many time, this series. This is an
RFC to know what people think about how to use them, the interface
proposed, whatever.
* simplify optional subsections moving the "needed" function to
vmstate description. I think that this simplification makes sense
by itself, it is indipendent of the rest of the patches.
* runstate: To make an example of an optional section, I decided to
use current runstate. Right now, we have a problem when:
- we start destination without -S
- we run migration, and it causes an ioerror on source, but migration finishes
- we try to run migration on destination anyways, when it is
possible that we could get disk corruption (the ioerror was there for a reason)
Luiz: You can see any obvious improvement about how we use runstates?
Laine: Could you told me if you (libvirt) like this or would want
something a bit different?
* I sent that option indpendently for new machine types.
* For old machine types I use this as one example of optional section.
We only sent it when the state is different from "running" or "paused".
So, the only case where we fail is if we migrate to an old qemu and
there is one error.
* On the runstate subsection "postload" we can send any event for
anything that libvirt wants when migration finishes.
Laine, can you told us what libvirt would preffer for this?
Kevin: You asked for optional sections in the past for the block
layer, would this proposal be enough for you?
Please review, comment.
Thanks, Juan.
Juan Quintela (9):
migration: create savevm_state
migration: Use normal VMStateDescriptions for Subsections
runstate: Add runstate store
runstate: create runstate_index function
runstate: migration allows more transitions now
migration: create new section to store global state
global_state: Make section optional
vmstate: Create optional sections
migration: Add configuration section
cpus.c | 11 ++--
docs/migration.txt | 11 ++--
exec.c | 11 ++--
hw/acpi/ich9.c | 10 ++--
hw/acpi/piix4.c | 10 ++--
hw/block/fdc.c | 37 +++++-------
hw/char/serial.c | 41 +++++--------
hw/display/qxl.c | 11 ++--
hw/display/vga.c | 11 ++--
hw/i386/pc_piix.c | 3 +
hw/i386/pc_q35.c | 3 +
hw/ide/core.c | 32 ++++------
hw/ide/pci.c | 16 ++---
hw/input/pckbd.c | 22 ++++---
hw/input/ps2.c | 11 ++--
hw/intc/apic_common.c | 10 ++--
hw/isa/lpc_ich9.c | 10 ++--
hw/net/e1000.c | 11 ++--
hw/net/rtl8139.c | 11 ++--
hw/net/vmxnet3.c | 12 ++--
hw/pci-host/piix.c | 10 ++--
hw/scsi/scsi-bus.c | 11 ++--
hw/timer/hpet.c | 11 ++--
hw/timer/mc146818rtc.c | 23 ++++---
hw/usb/hcd-ohci.c | 11 ++--
hw/usb/redirect.c | 34 +++++------
hw/virtio/virtio.c | 10 ++--
include/migration/migration.h | 6 ++
include/migration/vmstate.h | 10 ++--
include/sysemu/sysemu.h | 2 +
migration/migration.c | 114 ++++++++++++++++++++++++++++++++++-
migration/vmstate.c | 27 ++++++---
savevm.c | 135 ++++++++++++++++++++++++++++++++----------
target-arm/machine.c | 26 ++++----
target-i386/machine.c | 81 ++++++++++---------------
target-ppc/machine.c | 62 ++++++++-----------
target-s390x/machine.c | 21 +++----
vl.c | 27 +++++++++
38 files changed, 508 insertions(+), 407 deletions(-)
--
2.4.0
next reply other threads:[~2015-05-14 16:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 16:28 Juan Quintela [this message]
2015-05-14 16:28 ` [Qemu-devel] [PATCH 1/9] migration: create savevm_state Juan Quintela
2015-05-18 9:15 ` Dr. David Alan Gilbert
2015-05-14 16:28 ` [Qemu-devel] [PATCH 2/9] migration: Use normal VMStateDescriptions for Subsections Juan Quintela
2015-05-18 9:54 ` Dr. David Alan Gilbert
2015-05-14 16:28 ` [Qemu-devel] [PATCH 3/9] runstate: Add runstate store Juan Quintela
2015-05-18 10:35 ` Dr. David Alan Gilbert
2015-06-17 0:28 ` Juan Quintela
2015-05-18 10:38 ` Denis V. Lunev
2015-05-18 14:50 ` Eric Blake
2015-06-17 0:55 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 4/9] runstate: create runstate_index function Juan Quintela
2015-05-18 9:58 ` Dr. David Alan Gilbert
2015-05-18 14:55 ` Eric Blake
2015-06-17 0:31 ` Juan Quintela
2015-06-17 0:55 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 5/9] runstate: migration allows more transitions now Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 6/9] migration: create new section to store global state Juan Quintela
2015-05-18 10:23 ` Dr. David Alan Gilbert
2015-06-17 1:10 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 7/9] global_state: Make section optional Juan Quintela
2015-05-18 11:03 ` Dr. David Alan Gilbert
2015-06-17 1:25 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 8/9] vmstate: Create optional sections Juan Quintela
2015-05-18 11:23 ` Dr. David Alan Gilbert
2015-05-19 9:17 ` Dr. David Alan Gilbert
2015-05-14 16:28 ` [Qemu-devel] [PATCH 9/9] migration: Add configuration section Juan Quintela
2015-05-18 11:39 ` Dr. David Alan Gilbert
2015-06-17 1:39 ` 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=1431620920-19710-1-git-send-email-quintela@redhat.com \
--to=quintela@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 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).