From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Will Deacon <will@kernel.org>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] KVM: arm64: Fixes for parallel faults series
Date: Wed, 16 Nov 2022 16:56:53 +0000 [thread overview]
Message-ID: <20221116165655.2649475-1-oliver.upton@linux.dev> (raw)
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}.
Applies to the parallel faults series picked up last week.
v2: https://lore.kernel.org/kvmarm/20221115225502.2240227-1-oliver.upton@linux.dev/
v2 -> v3:
- Pass a pointer to the walker instead of a bool (Marc)
- Apply the aforementioned change to kvm_dereference_pteref()
Oliver Upton (2):
KVM: arm64: Take a pointer to walker data in kvm_dereference_pteref()
KVM: arm64: Don't acquire RCU read lock for exclusive table walks
arch/arm64/include/asm/kvm_pgtable.h | 154 +++++++++++++++------------
arch/arm64/kvm/hyp/pgtable.c | 10 +-
2 files changed, 88 insertions(+), 76 deletions(-)
--
2.38.1.431.g37b22c650d-goog
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kvmarm@lists.linux.dev, Will Deacon <will@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH v3 0/2] KVM: arm64: Fixes for parallel faults series
Date: Wed, 16 Nov 2022 16:56:53 +0000 [thread overview]
Message-ID: <20221116165655.2649475-1-oliver.upton@linux.dev> (raw)
Message-ID: <20221116165653.bpVuoIQyVyZc66EXwCJBErEcMWCvvwGDY-v-sNMTBZc@z> (raw)
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}.
Applies to the parallel faults series picked up last week.
v2: https://lore.kernel.org/kvmarm/20221115225502.2240227-1-oliver.upton@linux.dev/
v2 -> v3:
- Pass a pointer to the walker instead of a bool (Marc)
- Apply the aforementioned change to kvm_dereference_pteref()
Oliver Upton (2):
KVM: arm64: Take a pointer to walker data in kvm_dereference_pteref()
KVM: arm64: Don't acquire RCU read lock for exclusive table walks
arch/arm64/include/asm/kvm_pgtable.h | 154 +++++++++++++++------------
arch/arm64/kvm/hyp/pgtable.c | 10 +-
2 files changed, 88 insertions(+), 76 deletions(-)
--
2.38.1.431.g37b22c650d-goog
next reply other threads:[~2022-11-16 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:56 Oliver Upton [this message]
2022-11-16 16:56 ` [PATCH v3 0/2] KVM: arm64: Fixes for parallel faults series Oliver Upton
2022-11-16 16:56 ` [PATCH v3 1/2] KVM: arm64: Take a pointer to walker data in kvm_dereference_pteref() Oliver Upton
2022-11-16 16:56 ` Oliver Upton
2022-11-16 16:56 ` [PATCH v3 2/2] KVM: arm64: Don't acquire RCU read lock for exclusive table walks Oliver Upton
2022-11-16 16:56 ` Oliver Upton
2022-11-17 17:49 ` Will Deacon
2022-11-17 17:49 ` Will Deacon
2022-11-17 18:23 ` Oliver Upton
2022-11-17 18:23 ` Oliver Upton
2022-11-18 12:19 ` Will Deacon
2022-11-18 12:19 ` Will Deacon
2022-11-18 17:12 ` Oliver Upton
2022-11-18 17:12 ` Oliver Upton
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=20221116165655.2649475-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--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=maz@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).