From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56874)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1ZlwTi-0005Va-5y
	for qemu-devel@nongnu.org; Tue, 13 Oct 2015 06:06:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1ZlwTe-00033v-Rr
	for qemu-devel@nongnu.org; Tue, 13 Oct 2015 06:06:42 -0400
Received: from mailout1.w1.samsung.com ([210.118.77.11]:56343)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <p.fedin@samsung.com>) id 1ZlwTe-00031y-ME
	for qemu-devel@nongnu.org; Tue, 13 Oct 2015 06:06:38 -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 <0NW500G2ELEY23A0@mailout1.w1.samsung.com> for
	qemu-devel@nongnu.org; Tue, 13 Oct 2015 11:06:34 +0100 (BST)
From: Pavel Fedin <p.fedin@samsung.com>
References: <008b01d101be$0228d720$067a8560$@samsung.com>
	<20151009152942.GF2702@work-vm>
In-reply-to: <20151009152942.GF2702@work-vm>
Date: Tue, 13 Oct 2015 13:06:33 +0300
Message-id: <00b801d1059e$d6d4ffb0$847eff10$@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-language: ru
Subject: Re: [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: "'Dr. David Alan Gilbert'" <dgilbert@redhat.com>
Cc: 'QEMU' <qemu-devel@nongnu.org>

 Hello!

 Sorry for the delayed reply.

> What's an ITS ?

 Interrupt Translation Service. In a short, it's a thing responsible for handling PCIe MSI-X
interrupts on ARM64 architecture.

> With a related question, how big are the tables and can it change during the iterated part
> of the migrate?

 Tables are something like 64K each. They hold mappings between device/event IDs and actual IRQ
numbers.
 Unfortunately i don't know how to answer the second part of the question, about iterated part. Can
you explain in details, what is it and how does it work?
 Or, well, we could put the question the other way: imagine that in pre_save i tell my emulated
device to flush its cached state into RAM-based tables. In post_load i could tell the device to
re-read data from RAM into its cache. So, what do i need in order to make these tables in RAM to
migrate correctly?

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