[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9Lg1ESUVJov0WpH@google.com>
Date: Thu, 26 Jan 2023 20:21:40 +0000
From: Oliver Upton <oliver.upton@...ux.dev>
To: Gavin Shan <gshan@...hat.com>
Cc: kvmarm@...ts.linux.dev, kvmarm@...ts.cs.columbia.edu,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, pbonzini@...hat.com, corbet@....net,
maz@...nel.org, will@...nel.org, ricarkol@...gle.com,
eric.auger@...hat.com, yuzhe@...china.com, renzhengeek@...il.com,
reijiw@...gle.com, ardb@...nel.org, Julia.Lawall@...ia.fr,
yuzenghui@...wei.com, seanjc@...gle.com, shan.gavin@...il.com
Subject: Re: [PATCH v2 0/3] Improve dirty ring warning report
On Fri, Jan 20, 2023 at 07:44:02AM +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] adds unified helper vgic_write_guest_lock()
> PATCH[2 - 3] allows no-running-vcpu context for (a) and (b)
Besides the issue with the first patch, for the series:
Reviewed-by: Oliver Upton <oliver.upton@...ux.dev>
--
Thanks,
Oliver
Powered by blists - more mailing lists