From: Oliver Upton <oupton@google.com>
To: Ricardo Koller <ricarkol@google.com>
Cc: kvm@vger.kernel.org, andre.przywara@arm.com, pshier@google.com,
maz@kernel.org, pbonzini@redhat.com,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v3 0/4] KVM: arm64: vgic: Misc ITS fixes
Date: Tue, 10 May 2022 18:21:01 +0000 [thread overview]
Message-ID: <YnqtDT+EebIc0eVX@google.com> (raw)
In-Reply-To: <20220510001633.552496-1-ricarkol@google.com>
Hi Ricardo,
On Mon, May 09, 2022 at 05:16:29PM -0700, Ricardo Koller wrote:
> The purpose of this series is to help debugging failed ITS saves and
> restores. Failures can be due to misconfiguration on the guest side:
> tables with bogus base addresses, or the guest overwriting L1 indirect
> tables. KVM can't do much in these cases, but one thing it can do to help
> is raising errors as soon as possible.
For the series:
Reviewed-by: Oliver Upton <oupton@google.com>
--
Thanks,
Oliver
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2022-05-10 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 0:16 [PATCH v3 0/4] KVM: arm64: vgic: Misc ITS fixes Ricardo Koller
2022-05-10 0:16 ` [PATCH v3 1/4] KVM: arm64: vgic: Check that new ITEs could be saved in guest memory Ricardo Koller
2022-05-10 0:16 ` [PATCH v3 2/4] KVM: arm64: vgic: Add more checks when restoring ITS tables Ricardo Koller
2022-05-10 0:16 ` [PATCH v3 3/4] KVM: arm64: vgic: Do not ignore vgic_its_restore_cte failures Ricardo Koller
2022-05-10 0:16 ` [PATCH v3 4/4] KVM: arm64: vgic: Undo work in failed ITS restores Ricardo Koller
2022-05-10 18:21 ` Oliver Upton [this message]
2022-05-16 13:05 ` [PATCH v3 0/4] KVM: arm64: vgic: Misc ITS fixes Marc Zyngier
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=YnqtDT+EebIc0eVX@google.com \
--to=oupton@google.com \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
--cc=ricarkol@google.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