From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: ali saeedi <ali.saeedi56@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU_VM_SECTION START/END/PART/FULL
Date: Thu, 4 May 2017 16:36:03 +0100 [thread overview]
Message-ID: <20170504153602.GC2078@work-vm> (raw)
In-Reply-To: <CAGKXQyfNiBsRr832X6gQZZxkhnWYk0cqVvjPeGQPoCKF8e+9-Q@mail.gmail.com>
* ali saeedi (ali.saeedi56@gmail.com) wrote:
> Hi
> What are "QEMU_VM_SECTION START/END/PART/FULL" in savevm.c ?
> please explain them to me.
A QEMU migration stream is a sequence of 'sections'.
There are 4 (main) types of section:
FULL: The entire contents of a device - that's most cases
START: The start of a devices data that we're going to save
split across multiple sections
PART: More of a device previously that we had already sent a
START for
END: The end of a device that we sent a START for
Most devices we can send in one go (FULL); but some devices
are 'iterative' and need to be broken up into chunks - RAM is
the most common example because it's a lot of data that changes as
we're saving it.
Dave
> thanks a lot.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2017-05-04 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 13:31 [Qemu-devel] QEMU_VM_SECTION START/END/PART/FULL ali saeedi
2017-05-04 15:36 ` Dr. David Alan Gilbert [this message]
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=20170504153602.GC2078@work-vm \
--to=dgilbert@redhat.com \
--cc=ali.saeedi56@gmail.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.