* [Qemu-devel] QEMU_VM_SECTION START/END/PART/FULL
@ 2017-05-04 13:31 ali saeedi
2017-05-04 15:36 ` Dr. David Alan Gilbert
0 siblings, 1 reply; 2+ messages in thread
From: ali saeedi @ 2017-05-04 13:31 UTC (permalink / raw)
To: qemu-devel
Hi
What are "QEMU_VM_SECTION START/END/PART/FULL" in savevm.c ?
please explain them to me.
thanks a lot.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] QEMU_VM_SECTION START/END/PART/FULL
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
0 siblings, 0 replies; 2+ messages in thread
From: Dr. David Alan Gilbert @ 2017-05-04 15:36 UTC (permalink / raw)
To: ali saeedi; +Cc: qemu-devel
* 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-05-04 15:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).