Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp111742pxf; Wed, 24 Mar 2021 22:59:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwMC1uW2o9WcA946o0E+78i7BZvsilUqeKf3Y7vSsCUEgyV5+5m1yPwE03/jUS1lx8Y4J7J X-Received: by 2002:a05:6402:51d0:: with SMTP id r16mr7164914edd.48.1616651992432; Wed, 24 Mar 2021 22:59:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616651992; cv=none; d=google.com; s=arc-20160816; b=mY2ZHFqeQ1aTwyPR8k8eQg/MgFqHUQ3Y8dwRQrvlV9ez4Zno6Mqxj5isCmjuICQi0q raGsOskuwmtgMN9TVPpq7d8fuy7DbXoakvRe9CL8z+4/0ejW8owv1+JpcymzYf84OQzu Skyt2262N2FnA8+GUjJGMCTqyi5ENLX10w4ctMA3gUuMhjPTFINIXGsiQNMbfeoaQhIS kTt7/8RBCialHxWSF9RPQEi0+mWBfX7kxhsbZi4ZBRK8cCDua9n183P4rvPOS5rLqtck pnAyLND/QeUDnyDRhtzzXKAzbX+Juiqua5iVGqMy0q0qFnmCm4k25hFKqDolVlfL5wIX bsmA== 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=g6lI5wHf8qSazopXC2q7mSZqwnvybZZKhlpWaNweFZw=; b=kfs37GXrT/PUzEMtzo+bMRPUmAp9aAX9zemorunWzQ3/GSecERjjkKdTucql0zC8A+ n4NCZIPTvVlijsQtjQKZjLHonCYXSxrqCuv5eefXdUoTol/NvkHA8K+9rr1q71j5M8RD f+3njhKzNEObn9Zmxcl6wFDaxP7pVqXl8V0AzyM0TQYU/hQ1aH3VA6RSq4KnkvtTQqU5 6eNjVNNlo31hEO8acHN7oQMUg/vH4t3GURN6v/x1T2YQTpj/DwUxPYgomDoVPJI2x4sK nfYKqjH+d8KJgwo5P5mKDY2EI3PERxVpk57NKRUrrZOEX7FJJKG0N6wG0HVVKkra+AgS FB2Q== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u9si3594363ejx.635.2021.03.24.22.59.26; Wed, 24 Mar 2021 22:59:52 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229547AbhCYF4x (ORCPT + 99 others); Thu, 25 Mar 2021 01:56:53 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:14468 "EHLO szxga05-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229448AbhCYF4Y (ORCPT ); Thu, 25 Mar 2021 01:56:24 -0400 Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4F5Z71353SzwPVX; Thu, 25 Mar 2021 13:54:21 +0800 (CST) Received: from [10.174.184.135] (10.174.184.135) by DGGEMS407-HUB.china.huawei.com (10.3.19.207) with Microsoft SMTP Server id 14.3.498.0; Thu, 25 Mar 2021 13:56:11 +0800 Subject: Re: [PATCH v5 0/6] KVM: arm64: Add VLPI migration support on GICv4.1 To: Marc Zyngier , Will Deacon , , , Eric Auger , , CC: Alex Williamson , , , Lorenzo Pieralisi , Cornelia Huck References: <20210322060158.1584-1-lushenming@huawei.com> <161660992482.2080654.11109199563385851665.b4-ty@kernel.org> From: Shenming Lu Message-ID: <5c966333-97ec-aa52-068e-b037b42baf2c@huawei.com> Date: Thu, 25 Mar 2021 13:56:11 +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: <161660992482.2080654.11109199563385851665.b4-ty@kernel.org> 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 On 2021/3/25 2:19, Marc Zyngier wrote: > On Mon, 22 Mar 2021 14:01:52 +0800, Shenming Lu wrote: >> 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 series. >> >> 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. >> >> [...] > > Applied to next, thanks! Thanks a lot again for all the comments and suggestions. :-) Shenming > > [1/6] irqchip/gic-v3-its: Add a cache invalidation right after vPE unmapping > commit: 301beaf19739cb6e640ed44e630e7da993f0ecc8 > [2/6] irqchip/gic-v3-its: Drop the setting of PTZ altogether > commit: c21bc068cdbe5613d3319ae171c3f2eb9f321352 > [3/6] KVM: arm64: GICv4.1: Add function to get VLPI state > commit: 80317fe4a65375fae668672a1398a0fb73eb9023 > [4/6] KVM: arm64: GICv4.1: Try to save VLPI state in save_pending_tables > commit: f66b7b151e00427168409f8c1857970e926b1e27 > [5/6] KVM: arm64: GICv4.1: Restore VLPI pending state to physical side > commit: 12df7429213abbfa9632ab7db94f629ec309a58b > [6/6] KVM: arm64: GICv4.1: Give a chance to save VLPI state > commit: 8082d50f4817ff6a7e08f4b7e9b18e5f8bfa290d > > Cheers, > > M. >