summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSebastian Ene <sebastianene@google.com>2024-06-13 13:20:34 +0000
committerOliver Upton <oliver.upton@linux.dev>2024-06-14 20:28:30 +0000
commit0dd60c4632a1f517e384c318c7b33f4b3915c0a7 (patch)
tree3638a9e334cbb7b46dbc2c3385c5c003bfb3ff09
parent894376385a2d80a96816449e4991587a9a5ef0dd (diff)
downloadlwn-0dd60c4632a1f517e384c318c7b33f4b3915c0a7.tar.gz
lwn-0dd60c4632a1f517e384c318c7b33f4b3915c0a7.zip
KVM: arm64: Update the identification range for the FF-A smcs
The FF-A spec 1.2 reserves the following ranges for identifying FF-A calls: 0x84000060-0x840000FF: FF-A 32-bit calls 0xC4000060-0xC40000FF: FF-A 64-bit calls. Use the range identification according to the spec and allow calls that are currently out of the range(eg. FFA_MSG_SEND_DIRECT_REQ2) to be identified correctly. Acked-by: Will Deacon <will@kernel.org> Signed-off-by: Sebastian Ene <sebastianene@google.com> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com> Tested-by: Sudeep Holla <sudeep.holla@arm.com> Acked-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20240613132035.1070360-4-sebastianene@google.com Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
-rw-r--r--arch/arm64/kvm/hyp/include/nvhe/ffa.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm64/kvm/hyp/include/nvhe/ffa.h b/arch/arm64/kvm/hyp/include/nvhe/ffa.h
index d9fd5e6c7d3c..146e0aebfa1c 100644
--- a/arch/arm64/kvm/hyp/include/nvhe/ffa.h
+++ b/arch/arm64/kvm/hyp/include/nvhe/ffa.h
@@ -9,7 +9,7 @@
#include <asm/kvm_host.h>
#define FFA_MIN_FUNC_NUM 0x60
-#define FFA_MAX_FUNC_NUM 0x7F
+#define FFA_MAX_FUNC_NUM 0xFF
int hyp_ffa_init(void *pages);
bool kvm_host_ffa_handler(struct kvm_cpu_context *host_ctxt, u32 func_id);