From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Eric Auger <eric.auger@redhat.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
Shenming Lu <lushenming@huawei.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
yuzenghui@huawei.com, wanghaibin.wang@huawei.com,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH v5 0/6] KVM: arm64: Add VLPI migration support on GICv4.1
Date: Wed, 24 Mar 2021 18:19:25 +0000 [thread overview]
Message-ID: <161660992482.2080654.11109199563385851665.b4-ty@kernel.org> (raw)
In-Reply-To: <20210322060158.1584-1-lushenming@huawei.com>
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!
[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.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-03-24 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 6:01 Shenming Lu
2021-03-22 6:01 ` [PATCH v5 1/6] irqchip/gic-v3-its: Add a cache invalidation right after vPE unmapping Shenming Lu
2021-03-22 6:01 ` [PATCH v5 2/6] irqchip/gic-v3-its: Drop the setting of PTZ altogether Shenming Lu
2021-03-22 6:01 ` [PATCH v5 3/6] KVM: arm64: GICv4.1: Add function to get VLPI state Shenming Lu
2021-03-22 6:01 ` [PATCH v5 4/6] KVM: arm64: GICv4.1: Try to save VLPI state in save_pending_tables Shenming Lu
2021-03-22 6:01 ` [PATCH v5 5/6] KVM: arm64: GICv4.1: Restore VLPI pending state to physical side Shenming Lu
2021-03-22 6:01 ` [PATCH v5 6/6] KVM: arm64: GICv4.1: Give a chance to save VLPI state Shenming Lu
2021-03-24 18:19 ` Marc Zyngier [this message]
2021-03-25 5:56 ` [PATCH v5 0/6] KVM: arm64: Add VLPI migration support on GICv4.1 Shenming Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161660992482.2080654.11109199563385851665.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lushenming@huawei.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®