From: Marc Zyngier <maz@kernel.org>
To: James Morse <james.morse@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Alexandru Elisei <alexandru.elisei@arm.com>
Cc: Will Deacon <will@kernel.org>,
kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] KVM: arm64: Fixes for parallel faults series
Date: Tue, 22 Nov 2022 13:09:06 +0000 [thread overview]
Message-ID: <166912253823.898154.3075564690086280701.b4-ty@kernel.org> (raw)
In-Reply-To: <20221118182222.3932898-1-oliver.upton@linux.dev>
On Fri, 18 Nov 2022 18:22:19 +0000, Oliver Upton wrote:
> Small set of fixes for the parallel faults series. Most importantly,
> stop taking the RCU read lock for walking hyp stage-1. For the sake of
> consistency, take a pointer to kvm_pgtable_walker in
> kvm_dereference_pteref() as well.
>
> Tested on an Ampere Altra system with kvm-arm.mode={nvhe,protected} and
> lockdep. Applies on top of the parallel faults series picked up last
> week.
>
> [...]
Applied to next, thanks!
[1/3] KVM: arm64: Take a pointer to walker data in kvm_dereference_pteref()
commit: 3a5154c723ba5ceb9ce374a7307e03263c03fd29
[2/3] KVM: arm64: Don't acquire RCU read lock for exclusive table walks
commit: b7833bf202e3068abb77c642a0843f696e9c8d38
[3/3] KVM: arm64: Reject shared table walks in the hyp code
commit: 5e806c5812e8012a83496cf96bdba266b3aec428
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-11-22 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 18:22 [PATCH v4 0/3] KVM: arm64: Fixes for parallel faults series Oliver Upton
2022-11-18 18:22 ` [PATCH v4 1/3] KVM: arm64: Take a pointer to walker data in kvm_dereference_pteref() Oliver Upton
2022-11-18 18:22 ` [PATCH v4 2/3] KVM: arm64: Don't acquire RCU read lock for exclusive table walks Oliver Upton
2022-11-18 18:22 ` [PATCH v4 3/3] KVM: arm64: Reject shared table walks in the hyp code Oliver Upton
2022-11-21 18:09 ` [PATCH v4 0/3] KVM: arm64: Fixes for parallel faults series Will Deacon
2022-11-22 13:09 ` Marc Zyngier [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=166912253823.898154.3075564690086280701.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=will@kernel.org \
/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