tests: for the system workq in for obj tracing tests
The test relies on the workq thread being in the system. It is possible for the workq to not be in the system even if CONFIG_SYSTEM_WORKQUEUE is enabled, if nothing makes references to the symbols in the object file, so we cannot rely on the kconfig option to know if the system workq thread is in the system or not. So, force it in. Change-Id: I1ae2613fbd32928b673fc4c74a9dc56502255763 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
This commit is contained in:
parent
2375f05f2e
commit
5c2731f27f
2 changed files with 4 additions and 0 deletions
|
@ -50,6 +50,8 @@
|
|||
|
||||
#define TOTAL_THREADS (N_PHILOSOPHERS + 3 + IPM_THREAD)
|
||||
|
||||
void *force_sys_work_q_in = (void *)k_work_q_start;
|
||||
|
||||
#define OBJ_LIST_NAME k_mutex
|
||||
#define OBJ_LIST_TYPE struct k_mutex
|
||||
|
||||
|
|
|
@ -48,6 +48,8 @@
|
|||
* 1 IPM console thread
|
||||
*/
|
||||
|
||||
void *force_sys_work_q_in = (void *)k_work_q_start;
|
||||
|
||||
#define TOTAL_THREADS (N_PHILOSOPHERS + 3 + IPM_THREAD)
|
||||
|
||||
#define OBJ_LIST_NAME k_sem
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue