8cf56bcac7
Making a reference to the common work queue code should not necessarily drag in the system workqueue, since it is possible to use a workqueue that is not the system workqueue. This is done by moving the system workqueue into its own code module. Moving the system workqueue to its own code module allows removing the NANO_WORKQUEUE and SYSTEM_WORKQUEUE kconfig options, and compiling the common workqueue code and system workqueue all the time. They are only linked in the final image if a reference to them exist, same as the other kernel modules. Change-Id: I6f48d2542bda24f4702e7c2e317818dd082b3c11 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com> |
||
|---|---|---|
| .. | ||
| src | ||
| Makefile | ||
| prj.conf | ||
| prj.mdef | ||
| README.txt | ||
| testcase.ini | ||
Test Description ---------------- The object tracing test is a sanity test to verify that the object tracing API remains healthy. It uses the philsophers as an application that implements multiple taks that are synchronized with mutexes. The application initializes their objects and starts the philosophers' task interaction. A specific task, called object monitor, accesses the object tracing API and reports the number of expected objects. The sanity test script expects each test to finish its execution and then it considers the test completed. For that reason the philosophers' threads execute a finite number of iterations. After that the application execution ends.