optee: don't fail on unsuccessful device enumeration
Subsystems (2)
PATCH 1/1 optee: don't fail on unsuccessful device enumeration
optee_enumerate_devices() can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKed PTA_CMD_GET_DEVICES call. This should not result in driver initialization error because this is an optional feature.
Thus, it is better to print warning, instead of termination driver initialization.
--- drivers/tee/optee/core.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/tee/optee/core.c +2 -4
@@ -728,10 +728,8 @@ static int __init optee_driver_init(void)return PTR_ERR (optee); rc =optee_enumerate_devices (); -if (rc) { -optee_remove (optee); -return rc; - } +if (rc) +pr_warn ("can't enumerate optee devices: %d\n" , rc);pr_info ("initialized driver\n" );
Signature · 1 line
2.26.2
PATCH 1/1 optee: don't fail on unsuccessful device enumeration
optee_enumerate_devices() can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKed PTA_CMD_GET_DEVICES call. This should not result in driver initialization error because this is an optional feature.
Thus, it is better to print warning, instead of termination driver initialization.
---
resend: fixed email in s-o-b tag. Sorry for the noise
drivers/tee/optee/core.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
drivers/tee/optee/core.c +2 -4
@@ -728,10 +728,8 @@ static int __init optee_driver_init(void)return PTR_ERR (optee); rc =optee_enumerate_devices (); -if (rc) { -optee_remove (optee); -return rc; - } +if (rc) +pr_warn ("can't enumerate optee devices: %d\n" , rc);pr_info ("initialized driver\n" );
Signature · 1 line
2.26.2
Hi Volodymyr,
Quoted 11 lines · Volodymyr Babchuk
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall. This should not result in driver initialization error because this is an optional feature.Thus, it is better to print warning, instead of termination driver initialization.
Signed-off-by Volodymyr Babchuk <[email protected]>---
Looks good. Didn't apply directly at latest, but the conflict was easy enough to resolve.
I'll pick up this in a day unless someone objects.
I'll add a
Line.
Thanks,
Jens
Quoted 26 lines
resend: fixed email in s-o-b tag. Sorry for the noise
drivers/tee/optee/core.c| 6 ++----1 file changed, 2 insertions(+), 4 deletions(-)drivers/tee/optee/core.c +2
-5@@ -728,10 +728,8 @@ static int __init optee_driver_init(void)return PTR_ERR (optee); rc =optee_enumerate_devices (); -if (rc) { -optee_remove (optee); -return rc; - } +if (rc) +pr_warn ("can't enumerate optee devices: %d\n" , rc);pr_info ("initialized driver\n" ); --2.26.2
Hi Volodymyr,
Quoted 9 lines · Jens Wiklander
Hi Volodymyr,
Quoted 4 lines · Volodymyr Babchuk
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall.
Could you share a detailed description of the issue which you are facing? optee_enumerate_devices() is a simple invocation of pseudo TA and cases where OP-TEE doesn't provide corresponding pseudo TA are handled very well.
Quoted 2 lines
Quoted 2 lines
This should not result in driver
initialization error because this is an optional feature.
I wouldn't call it an optional feature as there might be real kernel drivers dependent on this enumeration. Also, it is a simple example to self test OP-TEE functionality too. So I am not sure how much functional OP-TEE would be if this basic TA invocation fails.
-Sumit
Quoted 45 lines
Quoted 6 lines
Thus, it is better to print warning, instead of termination driver initialization.
Signed-off-by Volodymyr Babchuk <[email protected]>---
Looks good. Didn't apply directly at latest, but the conflict was easy enough to resolve.
I'll pick up this in a day unless someone objects.
I'll add a
Fixes c3fa24af9244 ("tee: optee: add TEE bus device enumeration support")Line.
Thanks,
JensQuoted 26 lines
resend: fixed email in s-o-b tag. Sorry for the noise
drivers/tee/optee/core.c| 6 ++----1 file changed, 2 insertions(+), 4 deletions(-)drivers/tee/optee/core.c +2
-5@@ -728,10 +728,8 @@ static int __init optee_driver_init(void)return PTR_ERR (optee); rc =optee_enumerate_devices (); -if (rc) { -optee_remove (optee); -return rc; - } +if (rc) +pr_warn ("can't enumerate optee devices: %d\n" , rc);pr_info ("initialized driver\n" ); --2.26.2
Hi Sumit,
Quoted 10 lines · Sumit Garg
Hi Volodymyr,
Quoted 6 lines · Jens Wiklander
Hi Volodymyr,
Quoted 1 line · Volodymyr Babchuk
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall.Could you share a detailed description of the issue which you are facing?
optee_enumerate_devices()is a simple invocation of pseudo TA and cases where OP-TEE doesn't provide corresponding pseudo TA are handled very well.
Yes, I did some research and looks like issue is broader, than I expected. It is my fault, that I wasn't paying attention to the tee client support in the kernel. Basically, it is incompatible with the virtualization feature. You see, the main issue with virtual machines is the second stage MMU. Intermediate physical address, that appear to be contiguous for the kernel may be not contiguous in the real physical memory due to 2nd stage MMU mappings. This is the reason I introduced OPTEE_MSG_ATTR_NONCONTIG in the kernel driver.
But, looks like kernel-side optee client does not use this feature. It tries to provide SHM buffer as a simple contiguous span of memory. Xen
blocks calls with OPTEE_MSG_ATTR_TYPE_TMEM_* but withoutOPTEE_MSG_ATTR_NONCONTIG , because it can't translate IPAs to PAs for such buffers. This is why call to PTA_CMD_GET_DEVICES fails.
Valid fix would be to use OPTEE_MSG_ATTR_NONCONTIG whenever possible.
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
This should not result in driver
initialization error because this is an optional feature.I wouldn't call it an optional feature as there might be real kernel drivers dependent on this enumeration. Also, it is a simple example to self test OP-TEE functionality too. So I am not sure how much functional OP-TEE would be if this basic TA invocation fails.
Well, it fixed case when Xen is involved. I think, this is valid combination, when platform have the newest OP-TEE, but slightly older kernel. So, imagine that OP-TEE provides PTA_CMD_GET_DEVICES, but kernel can't use because it uses plain TMEM arguments,which are not supported in virtualized environment.
If there are kernel drivers, that depend on this PTA, they would not work in any case. But at least userspace clients still be able to use OP-TEE. This is why I call this feature "optional".
Signature · 2 lines
WBR Volodymyr Babchuk aka lorc [+380976646013] mailto: [email protected]
Hi Volodymyr,
Quoted 32 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 10 lines · Sumit Garg
Hi Volodymyr,
Quoted 6 lines · Jens Wiklander
Hi Volodymyr,
Quoted 1 line · Volodymyr Babchuk
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall.Could you share a detailed description of the issue which you are facing?
optee_enumerate_devices()is a simple invocation of pseudo TA and cases where OP-TEE doesn't provide corresponding pseudo TA are handled very well.Yes, I did some research and looks like issue is broader, than I expected. It is my fault, that I wasn't paying attention to the tee client support in the kernel. Basically, it is incompatible with the virtualization feature. You see, the main issue with virtual machines is the second stage MMU. Intermediate physical address, that appear to be contiguous for the kernel may be not contiguous in the real physical memory due to 2nd stage MMU mappings. This is the reason I introduced
OPTEE_MSG_ATTR_NONCONTIGin the kernel driver.
Quoted 8 lines
But, looks like kernel-side optee client does not use this feature. It tries to provide SHM buffer as a simple contiguous span of memory. Xen
blocks calls with OPTEE_MSG_ATTR_TYPE_TMEM_* but withoutOPTEE_MSG_ATTR_NONCONTIG, because it can't translate IPAs to PAs for such buffers. This is why call toPTA_CMD_GET_DEVICESfails.Valid fix would be to use
OPTEE_MSG_ATTR_NONCONTIGwhenever possible.
Thanks for the detailed analysis. It looks like you are missing the following fix patch in your tree which basically fixed broken tee_shm_alloc() in case dynamic shared memory is enabled (IIRC virtualization only supports dynamic shared memory).
commit a249dd200d03791cab23e47571f3e13d9c72af6c
Author: Sumit Garg <[email protected]> Date: Fri Nov 8 16:57:14 2019 +0530
tee: optee: Fix dynamic shm pool allocations
In case of dynamic shared memory pool, kernel memory allocated using dmabuf_mgr pool needs to be registered with OP-TEE prior to its usage during optee_open_session() or optee_invoke_func().
So fix dmabuf_mgr pool allocations via an additional call to optee_shm_register().
Also, allow kernel pages to be registered as shared memory with OP-TEE.
After this fix, your issue should be resolved as it uses OPTEE_MSG_ATTR_NONCONTIG attribute for kernel memory allocated via tee_shm_alloc().
Quoted 15 lines
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
This should not result in driver
initialization error because this is an optional feature.I wouldn't call it an optional feature as there might be real kernel drivers dependent on this enumeration. Also, it is a simple example to self test OP-TEE functionality too. So I am not sure how much functional OP-TEE would be if this basic TA invocation fails.
Well, it fixed case when Xen is involved. I think, this is valid combination, when platform have the newest OP-TEE, but slightly older kernel. So, imagine that OP-TEE provides
PTA_CMD_GET_DEVICES, but kernel can't use because it uses plain TMEM arguments,which are not supported in virtualized environment.
Quoted 3 lines
If there are kernel drivers, that depend on this PTA, they would not work in any case. But at least userspace clients still be able to use OP-TEE. This is why I call this feature "optional".
As you can see above, tee_shm_alloc() being broken in your case was detected via this simple pseudo TA invocation. So IMO, it would be better to keep the existing behaviour as it provides a kind of basic OP-TEE driver runtime self test too. Also, I think it would be a better user experience to have every OP-TEE interface working rather than a partially broken interface.
-Sumit
Quoted 4 lines
--
WBR Volodymyr Babchuk aka lorc [+380976646013]
mailto: [email protected]
Hi Sumit,
Quoted 45 lines · Sumit Garg
Hi Volodymyr,
Quoted 32 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 10 lines · Sumit Garg
Hi Volodymyr,
Quoted 6 lines · Jens Wiklander
Hi Volodymyr,
Quoted 1 line · Volodymyr Babchuk
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall.Could you share a detailed description of the issue which you are facing?
optee_enumerate_devices()is a simple invocation of pseudo TA and cases where OP-TEE doesn't provide corresponding pseudo TA are handled very well.Yes, I did some research and looks like issue is broader, than I expected. It is my fault, that I wasn't paying attention to the tee client support in the kernel. Basically, it is incompatible with the virtualization feature. You see, the main issue with virtual machines is the second stage MMU. Intermediate physical address, that appear to be contiguous for the kernel may be not contiguous in the real physical memory due to 2nd stage MMU mappings. This is the reason I introduced
OPTEE_MSG_ATTR_NONCONTIGin the kernel driver.Quoted 8 lines
But, looks like kernel-side optee client does not use this feature. It tries to provide SHM buffer as a simple contiguous span of memory. Xen
blocks calls with OPTEE_MSG_ATTR_TYPE_TMEM_* but withoutOPTEE_MSG_ATTR_NONCONTIG, because it can't translate IPAs to PAs for such buffers. This is why call toPTA_CMD_GET_DEVICESfails.Valid fix would be to use
OPTEE_MSG_ATTR_NONCONTIGwhenever possible.
Quoted 6 lines
Thanks for the detailed analysis. It looks like you are missing the following fix patch in your tree which basically fixed broken
tee_shm_alloc()in case dynamic shared memory is enabled (IIRC virtualization only supports dynamic shared memory).commit
a249dd200d03791cab23e47571f3e13d9c72af6c
Actually, I have this patch in my tree. So, it does not fixes the issue. Which is weird, actually. I'm planning to look deeper into this.
Quoted 20 lines
Quoted 16 lines
Quoted 9 lines
Quoted 4 lines
Quoted 4 lines
This should not result in driver
initialization error because this is an optional feature.I wouldn't call it an optional feature as there might be real kernel drivers dependent on this enumeration. Also, it is a simple example to self test OP-TEE functionality too. So I am not sure how much functional OP-TEE would be if this basic TA invocation fails.
Well, it fixed case when Xen is involved. I think, this is valid combination, when platform have the newest OP-TEE, but slightly older kernel. So, imagine that OP-TEE provides
PTA_CMD_GET_DEVICES, but kernel can't use because it uses plain TMEM arguments,which are not supported in virtualized environment.Quoted 3 lines
If there are kernel drivers, that depend on this PTA, they would not work in any case. But at least userspace clients still be able to use OP-TEE. This is why I call this feature "optional".
Quoted 6 lines
As you can see above,
tee_shm_alloc()being broken in your case was detected via this simple pseudo TA invocation. So IMO, it would be better to keep the existing behaviour as it provides a kind of basic OP-TEE driver runtime self test too. Also, I think it would be a better user experience to have every OP-TEE interface working rather than a partially broken interface.
I can see your point. But I think, that it is good to not to break backward- and forward- compatibility. Imagine, that user upgrades OP-TEE without changing the kernel. Previously it worked well, but new OP-TEE provides new PTA and kernel refuses to load the optee driver because driver fails to initialize that PTA.
This is basically what happened with me. Platform that I am using does not provide any OP-TEE devices so I assumed that I can safely ignore this feature. But, when I flashed the latest OP-TEE build I got dead optee driver. This is confusing from a user standpoint. You don't expect that firmware upgrade to another minor version will break existing setup. My proposed patch at least prints the warning, so user would know where to look...
Anyways, if we'll find a proper fix before next code freeze, I'd prefer to drop this particular patch. But let's keep it as a plan B. What do you think?
Signature · 2 lines
WBR Volodymyr Babchuk aka lorc [+380976646013] mailto: [email protected]
Hi Volodymyr,
Quoted 54 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 50 lines · Sumit Garg
Hi Volodymyr,
Quoted 32 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 10 lines · Sumit Garg
Hi Volodymyr,
Quoted 6 lines · Jens Wiklander
Hi Volodymyr,
Quoted 1 line · Volodymyr Babchuk
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall.Could you share a detailed description of the issue which you are facing?
optee_enumerate_devices()is a simple invocation of pseudo TA and cases where OP-TEE doesn't provide corresponding pseudo TA are handled very well.Yes, I did some research and looks like issue is broader, than I expected. It is my fault, that I wasn't paying attention to the tee client support in the kernel. Basically, it is incompatible with the virtualization feature. You see, the main issue with virtual machines is the second stage MMU. Intermediate physical address, that appear to be contiguous for the kernel may be not contiguous in the real physical memory due to 2nd stage MMU mappings. This is the reason I introduced
OPTEE_MSG_ATTR_NONCONTIGin the kernel driver.Quoted 8 lines
But, looks like kernel-side optee client does not use this feature. It tries to provide SHM buffer as a simple contiguous span of memory. Xen
blocks calls with OPTEE_MSG_ATTR_TYPE_TMEM_* but withoutOPTEE_MSG_ATTR_NONCONTIG, because it can't translate IPAs to PAs for such buffers. This is why call toPTA_CMD_GET_DEVICESfails.Valid fix would be to use
OPTEE_MSG_ATTR_NONCONTIGwhenever possible.Thanks for the detailed analysis. It looks like you are missing the following fix patch in your tree which basically fixed broken
tee_shm_alloc()in case dynamic shared memory is enabled (IIRC virtualization only supports dynamic shared memory).
Quoted 5 lines
Quoted 1 line
commit
a249dd200d03791cab23e47571f3e13d9c72af6cActually, I have this patch in my tree. So, it does not fixes the issue. Which is weird, actually. I'm planning to look deeper into this.
AFAICT, the only difference here is that it's the kernel memory registered rather than user-space memory. But I am not very conversant with the Xen environment. So I hope you will be able to find the root cause as to why Xen is blocking this invocation.
Quoted 34 lines
Quoted 21 lines
Quoted 17 lines
Quoted 10 lines
Quoted 5 lines
Quoted 5 lines
This should not result in driver
initialization error because this is an optional feature.I wouldn't call it an optional feature as there might be real kernel drivers dependent on this enumeration. Also, it is a simple example to self test OP-TEE functionality too. So I am not sure how much functional OP-TEE would be if this basic TA invocation fails.
Well, it fixed case when Xen is involved. I think, this is valid combination, when platform have the newest OP-TEE, but slightly older kernel. So, imagine that OP-TEE provides
PTA_CMD_GET_DEVICES, but kernel can't use because it uses plain TMEM arguments,which are not supported in virtualized environment.Quoted 3 lines
If there are kernel drivers, that depend on this PTA, they would not work in any case. But at least userspace clients still be able to use OP-TEE. This is why I call this feature "optional".
Quoted 6 lines
As you can see above,
tee_shm_alloc()being broken in your case was detected via this simple pseudo TA invocation. So IMO, it would be better to keep the existing behaviour as it provides a kind of basic OP-TEE driver runtime self test too. Also, I think it would be a better user experience to have every OP-TEE interface working rather than a partially broken interface.I can see your point. But I think, that it is good to not to break backward- and forward- compatibility. Imagine, that user upgrades OP-TEE without changing the kernel. Previously it worked well, but new OP-TEE provides new PTA and kernel refuses to load the optee driver because driver fails to initialize that PTA.
Quoted 7 lines
This is basically what happened with me. Platform that I am using does not provide any OP-TEE devices so I assumed that I can safely ignore this feature. But, when I flashed the latest OP-TEE build I got dead optee driver. This is confusing from a user standpoint. You don't expect that firmware upgrade to another minor version will break existing setup. My proposed patch at least prints the warning, so user would know where to look...
Warning prints aren't much useful in the sense that they can't be detected via current OP-TEE CI.
Quoted 4 lines
Anyways, if we'll find a proper fix before next code freeze, I'd prefer to drop this particular patch. But let's keep it as a plan B. What do you think?
Since it seems like currently the kernel internal interface is broken with virtualization support. So how about "plan B" being skipping the enumeration in case "OPTEE_SMC_SEC_CAP_VIRTUALIZATION" is set? As we can't expect to get TEE kernel drivers working without getting this interface fixed. Also, having an information message that the kernel internal interface is not supported with virtualization would be useful too.
-Sumit
Quoted 4 lines
--
WBR Volodymyr Babchuk aka lorc [+380976646013]
mailto: [email protected]
Hi Sumit,
Quoted 60 lines · Sumit Garg
Hi Volodymyr,
Quoted 56 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 51 lines · Sumit Garg
Hi Volodymyr,
Quoted 32 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 10 lines · Sumit Garg
Hi Volodymyr,
Quoted 6 lines · Jens Wiklander
Hi Volodymyr,
Quoted 1 line · Volodymyr Babchuk
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall.Could you share a detailed description of the issue which you are facing?
optee_enumerate_devices()is a simple invocation of pseudo TA and cases where OP-TEE doesn't provide corresponding pseudo TA are handled very well.Yes, I did some research and looks like issue is broader, than I expected. It is my fault, that I wasn't paying attention to the tee client support in the kernel. Basically, it is incompatible with the virtualization feature. You see, the main issue with virtual machines is the second stage MMU. Intermediate physical address, that appear to be contiguous for the kernel may be not contiguous in the real physical memory due to 2nd stage MMU mappings. This is the reason I introduced
OPTEE_MSG_ATTR_NONCONTIGin the kernel driver.Quoted 8 lines
But, looks like kernel-side optee client does not use this feature. It tries to provide SHM buffer as a simple contiguous span of memory. Xen
blocks calls with OPTEE_MSG_ATTR_TYPE_TMEM_* but withoutOPTEE_MSG_ATTR_NONCONTIG, because it can't translate IPAs to PAs for such buffers. This is why call toPTA_CMD_GET_DEVICESfails.Valid fix would be to use
OPTEE_MSG_ATTR_NONCONTIGwhenever possible.Thanks for the detailed analysis. It looks like you are missing the following fix patch in your tree which basically fixed broken
tee_shm_alloc()in case dynamic shared memory is enabled (IIRC virtualization only supports dynamic shared memory).commit
a249dd200d03791cab23e47571f3e13d9c72af6c
Quoted 8 lines
Quoted 3 lines
Actually, I have this patch in my tree. So, it does not fixes the issue. Which is weird, actually. I'm planning to look deeper into this.
AFAICT, the only difference here is that it's the kernel memory registered rather than user-space memory. But I am not very conversant with the Xen environment. So I hope you will be able to find the root cause as to why Xen is blocking this invocation.
Yes. I have found issue in Xen mediator code. It didn't allowed TMEM with NULL buf_ptr and without ATTR_NONCONTIG flag. This is clearly a bug and I already sent the patch to Xen ML.
Signature · 2 lines
WBR Volodymyr Babchuk aka lorc [+380976646013] mailto: [email protected]
Hi Volodymyr,
Quoted 68 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 64 lines · Sumit Garg
Hi Volodymyr,
Quoted 59 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 45 lines · Sumit Garg
Hi Volodymyr,
Quoted 32 lines · Volodymyr Babchuk
Hi Sumit,
Quoted 10 lines · Sumit Garg
Hi Volodymyr,
Quoted 6 lines · Jens Wiklander
Hi Volodymyr,
Quoted 1 line · Volodymyr Babchuk
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
optee_enumerate_devices()can fail for multiple of reasons. For example, I encountered issue when Xen OP-TEE mediator NACKedPTA_CMD_GET_DEVICEScall.Could you share a detailed description of the issue which you are facing?
optee_enumerate_devices()is a simple invocation of pseudo TA and cases where OP-TEE doesn't provide corresponding pseudo TA are handled very well.Yes, I did some research and looks like issue is broader, than I expected. It is my fault, that I wasn't paying attention to the tee client support in the kernel. Basically, it is incompatible with the virtualization feature. You see, the main issue with virtual machines is the second stage MMU. Intermediate physical address, that appear to be contiguous for the kernel may be not contiguous in the real physical memory due to 2nd stage MMU mappings. This is the reason I introduced
OPTEE_MSG_ATTR_NONCONTIGin the kernel driver.Quoted 8 lines
But, looks like kernel-side optee client does not use this feature. It tries to provide SHM buffer as a simple contiguous span of memory. Xen
blocks calls with OPTEE_MSG_ATTR_TYPE_TMEM_* but withoutOPTEE_MSG_ATTR_NONCONTIG, because it can't translate IPAs to PAs for such buffers. This is why call toPTA_CMD_GET_DEVICESfails.Valid fix would be to use
OPTEE_MSG_ATTR_NONCONTIGwhenever possible.Quoted 6 lines
Thanks for the detailed analysis. It looks like you are missing the following fix patch in your tree which basically fixed broken
tee_shm_alloc()in case dynamic shared memory is enabled (IIRC virtualization only supports dynamic shared memory).commit
a249dd200d03791cab23e47571f3e13d9c72af6cActually, I have this patch in my tree. So, it does not fixes the issue. Which is weird, actually. I'm planning to look deeper into this.
Quoted 9 lines
Quoted 4 lines
AFAICT, the only difference here is that it's the kernel memory registered rather than user-space memory. But I am not very conversant with the Xen environment. So I hope you will be able to find the root cause as to why Xen is blocking this invocation.
Yes. I have found issue in Xen mediator code. It didn't allowed TMEM with NULL
buf_ptrand withoutATTR_NONCONTIGflag. This is clearly a bug and I already sent the patch to Xen ML.
Glad to hear that you were able to find the bug and fix it.
BTW, I guess the reason you didn't notice this bug in user-space (xtest 1025) is due to missing kernel patch [1] (not yet in upstream) from your kernel tree.
[1] https://github.com/linaro-swg/linux/commit/1149e7d06a009e5dacf6aaa29bd087da64bfbed2
-Sumit
Quoted 3 lines
--
WBR Volodymyr Babchuk aka lorc [+380976646013]
mailto: [email protected]