path: root/Documentation/scheduler
diff options
authorTommaso Cucinotta <>2016-10-26 11:17:17 +0200
committerIngo Molnar <>2017-01-14 11:30:00 +0100
commit59f8c2989283bbd3df9fcfb22494d84f4852e536 (patch)
tree4a55cf07c8d352fde4e7222c0241de2e83adf7ad /Documentation/scheduler
parent5680d8094ffa9e5cfc81afdd865027ee6417c263 (diff)
sched/deadline: Show leftover runtime and abs deadline in /proc/*/sched
This patch allows for reading the current (leftover) runtime and absolute deadline of a SCHED_DEADLINE task through /proc/*/sched (entries dl.runtime and dl.deadline), while debugging/testing. Signed-off-by: Tommaso Cucinotta <> Signed-off-by: Peter Zijlstra (Intel) <> Reviewed-by: Juri Lelli <> Reviewed-by: Luca Abeni <> Acked-by: Daniel Bistrot de Oliveira <> Cc: Juri Lelli <> Cc: Linus Torvalds <> Cc: Mike Galbraith <> Cc: Peter Zijlstra <> Cc: Thomas Gleixner <> Link: Signed-off-by: Ingo Molnar <>
Diffstat (limited to 'Documentation/scheduler')
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/scheduler/sched-deadline.txt b/Documentation/scheduler/sched-deadline.txt
index 8e37b0ba2c9d..cbc1b46cbf70 100644
--- a/Documentation/scheduler/sched-deadline.txt
+++ b/Documentation/scheduler/sched-deadline.txt
@@ -408,6 +408,11 @@ CONTENTS
* the new scheduling related syscalls that manipulate it, i.e.,
sched_setattr() and sched_getattr() are implemented.
+ For debugging purposes, the leftover runtime and absolute deadline of a
+ SCHED_DEADLINE task can be retrieved through /proc/<pid>/sched (entries
+ dl.runtime and dl.deadline, both values in ns). A programmatic way to
+ retrieve these values from production code is under discussion.
4.3 Default behavior
@@ -476,6 +481,7 @@ CONTENTS
Still missing:
+ - programmatic way to retrieve current runtime and absolute deadline
- refinements to deadline inheritance, especially regarding the possibility
of retaining bandwidth isolation among non-interacting tasks. This is
being studied from both theoretical and practical points of view, and