Hi all,

 

I am proposing new changes to OS wrapper layer to help other RTOS use dynamic memory allocation.

 

OS wrapper layers help to create Mutex, Semaphores, and Thread on RTOS. The wrapper is designed to use static allocation of memory/objects

from predefined OS memory pool, which is not fully featured enough to allow dynamic memory allocation and freeing them after completion, if an RTOS

requires that kind of implementation.

For example, the child thread created in ns_test_helpers.c does a simple exit without passing a handle if the memory was dynamically allocated, which is a memory leak scenario.

 

Therefore os_wrapper_thread_suspend() and os_wrapper_thread_delete() are introduced to aid scenarios where dynamic memory allocation and freeing is required.

 

               In the current patch we just suspend the child thread and terminate it from parent thread.

 

The patch is open for review here: https://review.trustedfirmware.org/c/trusted-firmware-m/+/3294

 

Thanks & Best Regards,

Vikas Katariya

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.