OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/philosophers/prj.conf

8 lines
162 B
Plaintext
Raw Normal View History

tests: Few test require CONFIG_STDOUT_CONSOLE=n For some, "y" affects output, for some less tested platforms, leads to crashes. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2018-01-09 18:34:07 +08:00
CONFIG_STDOUT_CONSOLE=n
Dining philosophers demo for unified kernel. The demo can be configured to use different object types for its synchronization: SEMAPHORES, MUTEXES, STACKS, FIFOS and LIFOS. To configure a specific object, set the value of FORKS to one of these. By default, the demo uses MUTEXES. The demo can also be configured to work with static objects or dynamic objects. The behaviour will change depending if STATIC_OBJS is set to 0 or 1. By default, the demo uses dynamic objects. The demo can be configured to work with threads of the same priority or not. If using different priorities, two threads will be cooperative threads, and the other four will be preemtible threads; if using one priority, there will be six preemtible threads of priority 0. This is changed via SAME_PRIO. By default, the demo uses different priorities. The number of threads is set via NUM_PHIL. The demo has only been tested with six threads. In theory it should work with less than six threads, but not with more without making changes to the forks[] array in the phil_obj_abstract.h header file. Change-Id: If7a0a34b216929a661245fd921a32ec413df8a4a Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-09-15 00:28:27 +08:00
CONFIG_ASSERT=y
CONFIG_ASSERT_LEVEL=2
samples: configure philosophers with more than 32 priorities To have one project use more than 32 priorities. The preempt priorities are also aligned so that they straddle two priority bitmaps. Change-Id: I0f0862110d876e40fde45a0d105b769e8603d644 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-11-19 05:29:21 +08:00
CONFIG_NUM_COOP_PRIORITIES=29
CONFIG_NUM_PREEMPT_PRIORITIES=40
tests/sched/scheduler_api: samples/philosophers: Use SCHED_SCALABLE These two tests ask for lots of priority levels, more than the 32 maximum allowed by SCHED_MULTIQ (which is by design: if you have requirements like that DUMB or SCALABLE are better choices due to the RAM overhead of MULTIQ), so the build will fail on boards that defined MULTIQ as default. Don't let the platform choose the scheduler backend, ask for SCALABLE explicitly. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2018-06-29 02:17:18 +08:00
CONFIG_SCHED_SCALABLE=y
tests: More SMP disablement A few more test cases that are measurably unreliable when run in SMP. For the most part these work most of the time (though the semaphore one was pretty borderline -- I measured about 25% failures), but are measurably unstable against the backdrop of known qemu instability. Something is clearly going on and we need to come back to these to fix threadsafety issues. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2019-03-19 00:56:56 +08:00
CONFIG_SMP=n