michaelh/zephyr
1
0
Fork 0
Code Releases Activity

tests: for the system workq in for obj tracing tests

Browse source 
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:
Benjamin Walsh 2016-11-03 17:29:05 -04:00 • committed by Anas Nashif
commit 5c2731f27f
2 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
tests/legacy/kernel/test_obj_tracing/microkernel/src/object_monitor.c
View file

@ -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

2
tests/legacy/kernel/test_obj_tracing/nanokernel/src/object_monitor.c
View file

@ -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