[EXT_EP-11404] QNX memory utils does not support coherent thread safety for release/reimport Created: 01/Aug/23 Updated: 07/Dec/23 Resolved: 07/Dec/23 |
|
Status: | Fixed |
Project: | Embedded Software & Tools |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Medium |
Reporter: | TI User | Assignee: | TI User |
Resolution: | Fixed | Votes: | 0 |
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Product: | OpenVX Framework |
Internal ID: | TIOVX-1354 |
Forum URL: |
https://e2e.ti.com/e2eprivate/ford/ford-ep/f/ford-jacinto-forum/1244794/tda4vm-tiovx-bug-in-app_mem_qnx-c-appmemtranslatedmabuffd |
Found In Release: | TIOVX_08.06.00 |
Fix In Release: | TIOVX_09.01.00 |
Affected Platform/Device: | j721e-evm j721s2-evm j784s4-evm |
Description |
Overall functionality on QNX is broken based on both code review and some additional tests. For eg. a) Lack of thread safety for bufs array (all accesses shall be under mutex) Thus, although we temporary use patch checking bufs[i].phy_addr == 0 while searching buffers, they are looking for a coherent thread safe and release/reimport friendly delivery{} |