982402a99d
Many out of the POSIX subsystem configs are enabled automatically when merely CONFIG_POSIX_API is enabled, which is a prerequisite for many networking samples. This causes a massive experimental warning printout when building with warnings enabled. Since the new POSIX Kconfig configuration options are already present in Zephyr for 2 release cycles and seem settled, I suggest we move them out of experimental phase. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
20 lines
648 B
Plaintext
20 lines
648 B
Plaintext
# Copyright (c) 2023 Intel Corporation
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
menu "POSIX scheduler options"
|
|
|
|
config POSIX_PRIORITY_SCHEDULING
|
|
bool "POSIX priority-based process scheduling"
|
|
help
|
|
This enables POSIX scheduling APIs (_POSIX_PRIORITY_SCHEDULING).
|
|
|
|
Since Zephyr does not yet support processes, most of this behaviour is undefined, except for
|
|
use of sched_get_priority_min() and sched_get_priority_max().
|
|
|
|
For more information, please see
|
|
https://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_port.html#tag_24_03_04
|
|
https://pubs.opengroup.org/onlinepubs/9699919799/functions/sched_get_priority_max.html
|
|
|
|
endmenu
|