[rtems-central commit] spec: Clarify priority boosting
Sebastian Huber
sebh at rtems.org
Tue Jul 26 09:29:59 UTC 2022
Module: rtems-central
Branch: master
Commit: 8cb1607bd2c4e30d350446784f5a51fd147fe80c
Changeset: http://git.rtems.org/rtems-central/commit/?id=8cb1607bd2c4e30d350446784f5a51fd147fe80c
Author: Sebastian Huber <sebastian.huber at embedded-brains.de>
Date: Tue Jul 26 11:35:14 2022 +0200
spec: Clarify priority boosting
Change copyright according to RTEMS "doc/user/glossary.texi" history.
---
spec-glossary/glossary/priorityboosting.yml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/spec-glossary/glossary/priorityboosting.yml b/spec-glossary/glossary/priorityboosting.yml
index bb1e5295..63c0c490 100644
--- a/spec-glossary/glossary/priorityboosting.yml
+++ b/spec-glossary/glossary/priorityboosting.yml
@@ -1,6 +1,6 @@
SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
copyrights:
-- Copyright (C) 1988, 1998 On-Line Applications Research Corporation (OAR)
+- Copyright (C) 2015 embedded brains GmbH (http://www.embedded-brains.de)
enabled-by: true
glossary-type: term
links:
@@ -11,5 +11,6 @@ text: |
A simple approach to extend the priority inheritance protocol for
clustered scheduling is priority boosting. In case a mutex is owned by a
task of another cluster, then the priority of the owner task is raised to
- an artificially high priority, the pseudo-interrupt priority.
+ an artificially high priority. This approach is not used in RTEMS, see also
+ ${omip:/term}.
type: glossary
More information about the vc
mailing list