From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/3] KVM: arm64: Cleanups for managing SMCCC filter maple tree
Date: Wed, 4 Oct 2023 23:49:44 +0000 [thread overview]
Message-ID: <20231004234947.207507-1-oliver.upton@linux.dev> (raw)
Small series to clean up the way KVM manages the maple tree
representation of the SMCCC filter, only allocating nodes in the tree if
the SMCCC filter is used.
The other ugly bit that this fixes is the error path when 'reserved'
ranges cannot be inserted into the maple tree, instead returning an
error to userspace.
Oliver Upton (3):
KVM: arm64: Add a predicate for testing if SMCCC filter is configured
KVM: arm64: Only insert reserved ranges when SMCCC filter is used
KVM: arm64: Use mtree_empty() to determine if SMCCC filter configured
arch/arm64/include/asm/kvm_host.h | 4 +---
arch/arm64/kvm/hypercalls.c | 34 ++++++++++++++++++++-----------
2 files changed, 23 insertions(+), 15 deletions(-)
base-commit: 6465e260f48790807eef06b583b38ca9789b6072
--
2.42.0.609.gbb76f46606-goog
next reply other threads:[~2023-10-04 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 23:49 Oliver Upton [this message]
2023-10-04 23:49 ` [PATCH 1/3] KVM: arm64: Add a predicate for testing if SMCCC filter is configured Oliver Upton
2023-10-04 23:49 ` [PATCH 2/3] KVM: arm64: Only insert reserved ranges when SMCCC filter is used Oliver Upton
2023-10-04 23:49 ` [PATCH 3/3] KVM: arm64: Use mtree_empty() to determine if SMCCC filter configured Oliver Upton
2023-10-05 7:24 ` [PATCH 0/3] KVM: arm64: Cleanups for managing SMCCC filter maple tree Marc Zyngier
2023-10-05 20:55 ` 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=20231004234947.207507-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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.