From: Oliver Upton <oliver.upton@linux.dev>
To: Gavin Shan <gshan@redhat.com>
Cc: kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, pbonzini@redhat.com, corbet@lwn.net,
maz@kernel.org, will@kernel.org, ricarkol@google.com,
eric.auger@redhat.com, yuzhe@nfschina.com, renzhengeek@gmail.com,
reijiw@google.com, ardb@kernel.org, Julia.Lawall@inria.fr,
yuzenghui@huawei.com, seanjc@google.com, shan.gavin@gmail.com
Subject: Re: [PATCH v2 0/3] Improve dirty ring warning report
Date: Thu, 26 Jan 2023 20:21:40 +0000 [thread overview]
Message-ID: <Y9Lg1ESUVJov0WpH@google.com> (raw)
In-Reply-To: <20230119234405.349644-1-gshan@redhat.com>
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@linux.dev>
--
Thanks,
Oliver
prev parent reply other threads:[~2023-01-26 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 23:44 [PATCH v2 0/3] Improve dirty ring warning report Gavin Shan
2023-01-19 23:44 ` [PATCH v2 1/3] KVM: arm64: Add helper vgic_write_guest_lock() Gavin Shan
2023-01-26 20:20 ` Oliver Upton
2023-01-27 0:02 ` Gavin Shan
2023-01-19 23:44 ` [PATCH v2 2/3] KVM: arm64: Allow no running vcpu on restoring vgic3 LPI pending status Gavin Shan
2023-01-19 23:44 ` [PATCH v2 3/3] KVM: arm64: Allow no running vcpu on saving vgic3 pending table Gavin Shan
2023-01-26 20:21 ` Oliver Upton [this message]
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=Y9Lg1ESUVJov0WpH@google.com \
--to=oliver.upton@linux.dev \
--cc=Julia.Lawall@inria.fr \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=eric.auger@redhat.com \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=reijiw@google.com \
--cc=renzhengeek@gmail.com \
--cc=ricarkol@google.com \
--cc=seanjc@google.com \
--cc=shan.gavin@gmail.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
--cc=yuzhe@nfschina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.