From eec08efc9048111f47f42142c30a92683bf6756c Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 15 Jun 2016 06:59:57 +0200 Subject: posix: Rework sporadic server scheduling policy Instead of lowering the priority in case the initial budget is consumed raise the priority for each new period. Restore the normal priority once the initial budget is consumed. This makes it later easier to combine the high priority phase with temporary priority boosts (e.g. via priority ceiling and inheritance). Use the thread lock to protect the POSIX thread attributes instead of the thread state lock. This makes it easier to change the thread priority and keep the POSIX attributes consistent. Fixes a false positive use of uninitialized variable warning. --- cpukit/score/include/rtems/score/thread.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'cpukit/score/include/rtems/score/thread.h') diff --git a/cpukit/score/include/rtems/score/thread.h b/cpukit/score/include/rtems/score/thread.h index 7c5f0793c3..cde31b48c1 100644 --- a/cpukit/score/include/rtems/score/thread.h +++ b/cpukit/score/include/rtems/score/thread.h @@ -657,6 +657,7 @@ typedef struct { * provide their own lock. * * The thread lock protects the following thread variables + * - POSIX_API_Control::Attributes, * - Thread_Control::current_priority, * - Thread_Control::Wait::queue, and * - Thread_Control::Wait::operations. @@ -710,7 +711,6 @@ struct _Thread_Control { * The lock of this thread queue is used for various purposes. It protects * the following fields * - * - POSIX_API_Control::Attributes, * - RTEMS_API_Control::Signal, * - Thread_Control::budget_algorithm, * - Thread_Control::budget_callout, -- cgit v1.2.3