[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167501840046.2480538.4084679017095353524.b4-ty@kernel.org>
Date: Sun, 29 Jan 2023 18:54:10 +0000
From: Marc Zyngier <maz@...nel.org>
To: Gavin Shan <gshan@...hat.com>, kvmarm@...ts.linux.dev
Cc: linux-kernel@...r.kernel.org, will@...nel.org, reijiw@...gle.com,
kvm@...r.kernel.org, isaku.yamahata@...el.com, pbonzini@...hat.com,
suzuki.poulose@....com, eric.auger@...hat.com, yuzhe@...china.com,
yuzenghui@...wei.com, linux-doc@...r.kernel.org,
james.morse@....com, renzhengeek@...il.com, corbet@....net,
oliver.upton@...ux.dev, kvmarm@...ts.cs.columbia.edu,
shan.gavin@...il.com, seanjc@...gle.com, catalin.marinas@....com,
linux-arm-kernel@...ts.infradead.org, ricarkol@...gle.com
Subject: Re: [PATCH v3 0/4] Improve dirty ring warning report
On Fri, 27 Jan 2023 07:54:47 +0800, Gavin Shan wrote:
> It has been known case where no running VCPU context exists when the
> vgic/its tables are saved. There are other two unknown cases where we
> don't have the running VCPU context: (a) restore vgic3 LPI pending
> status. (b) restoring vgic3 pending tables.
>
> PATCH[1] includes 'kvm_mmu.h' to 'vgic.h'
> PATCH[2] adds unified helper vgic_write_guest_lock()
> PATCH[3 - 4] allows no-running-vcpu context for (a) and (b)
>
> [...]
Applied to fixes, thanks!
[2/4] KVM: arm64: Add helper vgic_write_guest_lock()
commit: a23eaf9368aafa4defcc8904b20391b6ea07bb1e
[3/4] KVM: arm64: Allow no running vcpu on restoring vgic3 LPI pending status
commit: 2f8b1ad2228a7f1f1e2458864f4bfc1cbdf511ed
[4/4] KVM: arm64: Allow no running vcpu on saving vgic3 pending table
commit: 6028acbe3a5f2119a2a6ddd3e06453c87c09cae0
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists