From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45626)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1Zk9Y1-0005Ki-Ex
	for qemu-devel@nongnu.org; Thu, 08 Oct 2015 07:39:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1Zk9Xw-0003tQ-D1
	for qemu-devel@nongnu.org; Thu, 08 Oct 2015 07:39:45 -0400
Received: from mailout1.w1.samsung.com ([210.118.77.11]:55626)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1Zk9Xw-0003tC-7Z
	for qemu-devel@nongnu.org; Thu, 08 Oct 2015 07:39:40 -0400
Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245])
	by mailout1.w1.samsung.com
	(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5
	2014)) with ESMTP id <0NVW00A21GE0G060@mailout1.w1.samsung.com> for
	qemu-devel@nongnu.org; Thu, 08 Oct 2015 12:39:36 +0100 (BST)
Received: from fedinw7x64 ([106.109.131.169])
	by eusync4.samsung.com (Oracle Communications Messaging Server
	7.0.5.31.0 64bit (built May  5 2014))
	with ESMTPA id <0NVW00928GDZM220@eusync4.samsung.com> for
	qemu-devel@nongnu.org; Thu, 08 Oct 2015 12:39:36 +0100 (BST)
From: Pavel Fedin <p.fedin@samsung.com>
Date: Thu, 08 Oct 2015 14:39:35 +0300
Message-id: <008b01d101be$0228d720$067a8560$@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-language: ru
Subject: [Qemu-devel] Live migration sequence
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: 'QEMU' <qemu-devel@nongnu.org>

 Hello!

 I would like to clarify, what is the exact live migration sequence in qemu?

 I mean - there are pre_save and post_load callbacks for VMState structures. Is there any determined
order of calling them related to memory contents migration? In other words, is there any guarantee
that pre_save is called before RAM migrates, and post_load is called after RAM migrates?
 The answer to this question is important for developing vITS live migration, where i have to dump
internal ITS state into in-memory tables before the migration starts, and then get it back in cache
on destination.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia