From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51283)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1ZmzZB-0005wX-Vu
	for qemu-devel@nongnu.org; Fri, 16 Oct 2015 03:36:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1ZmzZ6-0002s1-W9
	for qemu-devel@nongnu.org; Fri, 16 Oct 2015 03:36:41 -0400
Received: from mail-vk0-f41.google.com ([209.85.213.41]:33789)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1ZmzZ6-0002rx-S0
	for qemu-devel@nongnu.org; Fri, 16 Oct 2015 03:36:36 -0400
Received: by vkaw128 with SMTP id w128so63669085vka.0
	for <qemu-devel@nongnu.org>; Fri, 16 Oct 2015 00:36:36 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <00a501d107dd$7fd8b350$7f8a19f0$@samsung.com>
References: <010601d10747$569ae800$03d0b800$@samsung.com>
	<CAFEAcA-ndH_duvEL6vEBzVmU8uWqvJoVCzFEtHsvwFAYtnT2rg@mail.gmail.com>
	<00a501d107dd$7fd8b350$7f8a19f0$@samsung.com>
From: Peter Maydell <peter.maydell@linaro.org>
Date: Fri, 16 Oct 2015 08:36:17 +0100
Message-ID: <CAFEAcA8u1ak3fKrxfcH1esEpujUW9QKOUxez_2Gb_1QKNQnSRg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] [PATCH] arm_gic_kvm: Disable live migration if not
	supported
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: Pavel Fedin <p.fedin@samsung.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>

On 16 October 2015 at 07:40, Pavel Fedin <p.fedin@samsung.com> wrote:
>  Hello!
>
>> What kernel are you running that doesn't support state save/restore
>> in the GICv2 implementation?
>
>  I am not running such an old kernel. Just realized that GICv3 will need something similar, and actually GICv2 needs it too.
>  Actually this idea came to me when i occasionally tried to migrate a machine with an ITS. My ITS was missing unmigratable flag.

Yes, GICv3 will need to handle "no migration support". But this
is the GICv2 code. Unless there are kernels out in the wild
which support v2 but not migration, there's no need to check
for that situation here.

thanks
-- PMM