You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doxygen/history.dox
+18-1Lines changed: 18 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,29 @@
1
1
/*! @page history Revision History
2
2
3
-
@section qpc_7_1_0 Version 7.1.0, 2022-08-30 (planned)
3
+
@section qpc_7_1_0 Version 7.1.0, 2022-08-30
4
4
This QP/C release introduces [<b>preemption-threshold scheduling</b> (PTS)](https://www.state-machine.com/doc/Ghattas07.pdf) for the preemptive QK and QXK kernels. Specifically, it is now possible to limit preemption of a given QActive/QXThread by giving it both the QF-priority and preemption-threshold.
5
5
6
6
The following diagram shows the relationship between the "QF-priority" and "preemption-threshold" (see also ::QPrioSpec):
7
7
8
8

9
9
10
+
__Source__
11
+
- modified the QP/C code for preemption-threshold
12
+
- improved QS tracing of Scheduler activities in QK and QXK
13
+
- improved implementation of QXSemaphore and QXMutex in QXK
14
+
15
+
__Ports__
16
+
- Modified QK and QXK ports to ARM Cortex-M for preemption-threshold and for handling the context-switch callback
17
+
- Updated Zephyr port and examples for Zephyr 3.1.99
18
+
19
+
__Examples__
20
+
- Added Q_PRIO() macro for setting QF-priority and preemption-threshold to various examples (in calls to QACTIVE_START())
21
+
- increased size of the main stack in most examples from 1024 to 2048 bytes. This is to prevent stack overflow that was observed with the lower limit.
22
+
23
+
__Testing__
24
+
- modified QUTest to also allow testing of the QP framework itself.
25
+
26
+
10
27
@note
11
28
For backwards-compatibility, ::QPrioSpec data type might contain only the "QF-priority" component (and the "preemption-threshold" component left at zero). In that case, the "preemption-threshold" will be assumed to be the same as the "QF-priority". This corresponds exactly to the previous semantics of AO priority.
0 commit comments