Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1053696pxb; Fri, 26 Feb 2021 01:01:28 -0800 (PST) X-Google-Smtp-Source: ABdhPJw/kqSwLJ3fouFfcbfzb73UwNo8PhW5+pcB0F6mmR4p+dcAuIREUEGBiAhc4ACgyfKQ+Y/q X-Received: by 2002:a17:906:8043:: with SMTP id x3mr2130443ejw.149.1614330088575; Fri, 26 Feb 2021 01:01:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614330088; cv=none; d=google.com; s=arc-20160816; b=WNIu1fpdd0GcRoOAnGEOAYyqizB0U6k2v+x0EOK4jvJ05kuO8hPF3+etXp5CcQz5mM V7bSnSfbIfFwUq+PmMyqSnSAqpmmtM0TrHj2Xwfx2zMJChDsixybtJPTKn+qDYZpC/Ug 4JP8/++k2PQxD3Z4h5dW2f4uH4k6NdbPzIpUhQwpr2Ay8NZm1k4wSt/u6x66nOA8E+mI LRbF5xQdghy/MJQuHjverHYDPNNugaERxNlovlAIaW7sYTR2WqWU4AJcW8Ko/5kkpebn 4ycqyv2VL2NU409SqkUM7lcU+VQYuk+2baH4N4k+Bp28gqx3ZHxcAexnwYmhs+JIBdEy 7meg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=WIjII+E6BOFAcp6/w22g1ujoykjqULbTJNvVGtmgO/k=; b=okBI+mirwrzSGSx5yaogOCelIU6K/dEUbKO8zq5jEBy8lgqIRC8g4MkZERKn9WJX5Y aT3Mw42XIc5h1MojTjevFmfXHNvA2X7gOGa/BAojMq1N7DetM2YeSWwlSJ2TbKVOK7Tt dllnV1cx38ly+pjSU228kAopzVAgBHbm5Y9huKAi1TFNLowtg2ZlbXz6BoQbJQgDA/10 7uKzJ1mr6sWaSDfepxLRv8TtMlKGs8e/AVhBrA3+USi9MudJfk8Y6W1YDfMSIi+C0EYk 77UcG7jLFMxL7JMeidRx7phb+44ETCcbPj85Xh8XNbIfQ57RyQmnxwjeCCoMvb8co19y mSFg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e6si5931197edz.98.2021.02.26.01.01.05; Fri, 26 Feb 2021 01:01:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229999AbhBZI7v (ORCPT + 99 others); Fri, 26 Feb 2021 03:59:51 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:12953 "EHLO szxga06-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229537AbhBZI7p (ORCPT ); Fri, 26 Feb 2021 03:59:45 -0500 Received: from DGGEMS411-HUB.china.huawei.com (unknown [172.30.72.60]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4Dn3Sx46yyzjRhZ; Fri, 26 Feb 2021 16:57:37 +0800 (CST) Received: from [10.174.184.135] (10.174.184.135) by DGGEMS411-HUB.china.huawei.com (10.3.19.211) with Microsoft SMTP Server id 14.3.498.0; Fri, 26 Feb 2021 16:58:48 +0800 Subject: Re: [PATCH v3 0/4] KVM: arm64: Add VLPI migration support on GICv4.1 To: Marc Zyngier , Eric Auger , "Will Deacon" , , , , CC: Alex Williamson , Cornelia Huck , Lorenzo Pieralisi , , References: <20210127121337.1092-1-lushenming@huawei.com> From: Shenming Lu Message-ID: <4c2fdcc3-4189-6515-3a68-7bdf26e31973@huawei.com> Date: Fri, 26 Feb 2021 16:58:37 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: <20210127121337.1092-1-lushenming@huawei.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.184.135] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marc, Gentle ping. Does this series need any further modification? Wish you can pick it up. :-) Thanks, Shenming On 2021/1/27 20:13, Shenming Lu wrote: > Hi Marc, sorry for the late commit. > > In GICv4.1, migration has been supported except for (directly-injected) > VLPI. And GICv4.1 Spec explicitly gives a way to get the VLPI's pending > state (which was crucially missing in GICv4.0). So we make VLPI migration > capable on GICv4.1 in this patch set. > > In order to support VLPI migration, we need to save and restore all > required configuration information and pending states of VLPIs. But > in fact, the configuration information of VLPIs has already been saved > (or will be reallocated on the dst host...) in vgic(kvm) migration. > So we only have to migrate the pending states of VLPIs specially. > > Below is the related workflow in migration. > > On the save path: > In migration completion: > pause all vCPUs > | > call each VM state change handler: > pause other devices (just keep from sending interrupts, and > such as VFIO migration protocol has already realized it [1]) > | > flush ITS tables into guest RAM > | > flush RDIST pending tables (also flush VLPI state here) > | > ... > On the resume path: > load each device's state: > restore ITS tables (include pending tables) from guest RAM > | > for other (PCI) devices (paused), if configured to have VLPIs, > establish the forwarding paths of their VLPIs (and transfer > the pending states from kvm's vgic to VPT here) > > We have tested this series in VFIO migration, and found some related > issues in QEMU [2]. > > Links: > [1] vfio: UAPI for migration interface for device state: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a8a24f3f6e38103b77cf399c38eb54e1219d00d6 > [2] vfio: Some fixes and optimizations for VFIO migration: > https://patchwork.ozlabs.org/cover/1413263/ > > History: > > v2 -> v3 > - Add the vgic initialized check to ensure that the allocation and enabling > of the doorbells have already been done before unmapping the vPEs. > - Check all get_vlpi_state related conditions in save_pending_tables in one place. > - Nit fixes. > > v1 -> v2: > - Get the VLPI state from the KVM side. > - Nit fixes. > > Thanks, > Shenming > > > Shenming Lu (3): > KVM: arm64: GICv4.1: Add function to get VLPI state > KVM: arm64: GICv4.1: Try to save hw pending state in > save_pending_tables > KVM: arm64: GICv4.1: Give a chance to save VLPI's pending state > > Zenghui Yu (1): > KVM: arm64: GICv4.1: Restore VLPI's pending state to physical side > > .../virt/kvm/devices/arm-vgic-its.rst | 2 +- > arch/arm64/kvm/vgic/vgic-its.c | 6 +- > arch/arm64/kvm/vgic/vgic-v3.c | 61 +++++++++++++++++-- > arch/arm64/kvm/vgic/vgic-v4.c | 33 ++++++++++ > arch/arm64/kvm/vgic/vgic.h | 1 + > 5 files changed, 93 insertions(+), 10 deletions(-) >