Hi Volodymyr,
On 18/09/2019 19:51, Volodymyr Babchuk wrote:
OP-TEE mediator now is "Tech Preview" state, and we want to update it's description in Kconfig accordingly.
Signed-off-by: Volodymyr Babchuk volodymyr_babchuk@epam.com
Note to commiter: this patch depends on first 4 patches in the series.
xen/arch/arm/tee/Kconfig | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/xen/arch/arm/tee/Kconfig b/xen/arch/arm/tee/Kconfig index b4b6aa2610..a4a598191e 100644 --- a/xen/arch/arm/tee/Kconfig +++ b/xen/arch/arm/tee/Kconfig @@ -3,7 +3,11 @@ config OPTEE default n depends on TEE help
Enable experimental OP-TEE mediator. It allows guests to access
OP-TEE running on your platform. This requires virtualization-enabled
OP-TEE present. You can learn more about virtualization for OP-TEE
at https://optee.readthedocs.io/architecture/virtualization.html
Enable the OP-TEE mediator. It allows guests to access
OP-TEE running on your platform. This requires
virtualization-enabled OP-TEE present. You can learn more
about virtualization for OP-TEE at
https://optee.readthedocs.io/architecture/virtualization.html
Right now OP-TEE mediator is "Tech Preview" state, so it is
not good idea to use it in production.
Well, the whole TEE support is under "EXPERT" so someone selecting this option already know this should not be used in production. We also have SUPPORT.MD describing the state of the feature.
So I would drop completely the last sentence and potentially gate OPTEE with "EXPERT" as well. Note that the last bits is optional.
Cheers,