[Xen-changelog] [xen staging] xen/arm: optee: check if OP-TEE is virtualization-aware

[patchbot@xxxxxxx]

commit 68e0eb83ef62a4bbbd4837c3759bada65a62b71b
Author:     Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
AuthorDate: Wed Jun 19 17:54:24 2019 +0000
Commit:     Julien Grall <julien.grall@xxxxxxx>
CommitDate: Tue Jul 9 15:15:24 2019 +0100

    xen/arm: optee: check if OP-TEE is virtualization-aware
    
    This is workaround for OP-TEE 3.5. This is the first OP-TEE release
    which supports virtualization, but there is no way to tell if
    OP-TEE was built with that support enabled. We can probe for it
    by calling SMC that is available only when OP-TEE is built with
    virtualization support.
    
    Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@xxxxxxxx>
    Acked-by: Julien Grall <julien.grall@xxxxxxx>
---
 xen/arch/arm/tee/optee.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/xen/arch/arm/tee/optee.c b/xen/arch/arm/tee/optee.c
index 1d79c2c159..ec5402e89b 100644
--- a/xen/arch/arm/tee/optee.c
+++ b/xen/arch/arm/tee/optee.c
@@ -172,6 +172,16 @@ static bool optee_probe(void)
         return false;
     }
 
+    /*
+     * Workaround: OP-TEE 3.5 have no way to tell if it is build with
+     * virtualization support. But we can probe for OPTEE_SMC_VM_DESTROYED
+     * call. It will return OPTEE_SMC_RETURN_UNKNOWN_FUNCTION if
+     * OP-TEE have no virtualization support enabled.
+     */
+    arm_smccc_smc(OPTEE_SMC_VM_DESTROYED, 0, 0, 0, 0, 0, 0, 0, &resp);
+    if ( resp.a0 == OPTEE_SMC_RETURN_UNKNOWN_FUNCTION )
+        return false;
+
     return true;
 }
 
--
generated by git-patchbot for /home/xen/git/xen.git#staging

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog