You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In regular threadx, each thread can know is identity and basic data on himself by accessing its thread pointer using the global variable that holds current thread pointer (TX_THREAD_GET_CURRENT).
But in threadx modules (at least with memory protection) there is no (as far as I know) global that holding the current thread pointer. There is in the beginning of the stack of each thread TXM_MODULE_THREAD_ENTRY_INFO struct which holds also the thread pointer, but there is no global that holds pointer to the beginning of current stack, just _txm_module_entry_info which point to this struct in the start_stop thread.
Describe the solution you'd like
Some utility in module to get the pointer of current thread TXM_MODULE_THREAD_ENTRY_INFO.
Describe alternatives you've considered
Solution probably need to be done in the assembly level as part of the context switches and kernel-user switches, which is hard work, I would prefer easier solution
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In regular threadx, each thread can know is identity and basic data on himself by accessing its thread pointer using the global variable that holds current thread pointer (TX_THREAD_GET_CURRENT).
But in threadx modules (at least with memory protection) there is no (as far as I know) global that holding the current thread pointer. There is in the beginning of the stack of each thread TXM_MODULE_THREAD_ENTRY_INFO struct which holds also the thread pointer, but there is no global that holds pointer to the beginning of current stack, just _txm_module_entry_info which point to this struct in the start_stop thread.
Describe the solution you'd like
Some utility in module to get the pointer of current thread TXM_MODULE_THREAD_ENTRY_INFO.
Describe alternatives you've considered
Solution probably need to be done in the assembly level as part of the context switches and kernel-user switches, which is hard work, I would prefer easier solution
Additional context
The text was updated successfully, but these errors were encountered: