From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
David Brazdil <dbrazdil@google.com>,
Quentin Perret <qperret@google.com>,
Steven Price <steven.price@arm.com>,
Will Deacon <will@kernel.org>,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 fixes for 5.14, take #2
Date: Fri, 13 Aug 2021 07:42:41 +0100 [thread overview]
Message-ID: <20210813064241.2603475-1-maz@kernel.org> (raw)
Hi Paolo,
Here's the second batch of KVM/arm64 fixes for 5.14, and hopefully the
last for this cycle. We have another MTE fix from Steven, but also
have an off-by-one bug squashed by David in the protected memory path.
Please pull,
M.
The following changes since commit 5cf17746b302aa32a4f200cc6ce38865bfe4cf94:
KVM: arm64: selftests: get-reg-list: actually enable pmu regs in pmu sublist (2021-07-14 11:55:18 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-5.14-2
for you to fetch changes up to c4d7c51845af9542d42cd18a25c570583abf2768:
KVM: arm64: Fix race when enabling KVM_ARM_CAP_MTE (2021-07-29 17:34:01 +0100)
----------------------------------------------------------------
KVM/arm64 fixes for 5.14, take #2
- Plug race between enabling MTE and creating vcpus
- Fix off-by-one bug when checking whether an address range is RAM
----------------------------------------------------------------
David Brazdil (1):
KVM: arm64: Fix off-by-one in range_is_memory
Steven Price (1):
KVM: arm64: Fix race when enabling KVM_ARM_CAP_MTE
arch/arm64/kvm/arm.c | 12 ++++++++----
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 2 +-
2 files changed, 9 insertions(+), 5 deletions(-)
reply other threads:[~2021-08-13 6:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210813064241.2603475-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=dbrazdil@google.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pbonzini@redhat.com \
--cc=qperret@google.com \
--cc=steven.price@arm.com \
--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