aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2018-11-05 15:41:14 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2019-03-06 15:12:10 +0100
commit5fa62195f542a9f3ed4a824c4c11996b8b64ece0 (patch)
treebb3b9941fd6e1c29b6325385d3c749d580d6a01a
parentc3eba6648e4572799c0385b2c29699c2bba5e51e (diff)
downloadman-pages-5fa62195f542a9f3ed4a824c4c11996b8b64ece0.tar.gz
sched_setattr.2: Note that SCHED_FLAG_DL_OVERRUN SIGXCPU signal is process-directed
And further note that this is probably a bug. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man2/sched_setattr.221
1 files changed, 18 insertions, 3 deletions
diff --git a/man2/sched_setattr.2 b/man2/sched_setattr.2
index 235d575205..806ab67c86 100644
--- a/man2/sched_setattr.2
+++ b/man2/sched_setattr.2
@@ -172,14 +172,29 @@ thread to reclaim bandwidth unused by other real-time thread.
.TP
.BR SCHED_FLAG_DL_OVERRUN " (since Linux 4.16)"
.\" commit 34be39305a77b8b1ec9f279163c7cdb6cc719b91
-This flag allows a
+This flag allows an application to get informed about run-time overruns in
.BR SCHED_DEADLINE
-thread to get informed about run-time overruns,
-which may be caused by (for example) coarse execution time accounting
+threads.
+Such overruns may be caused by (for example) coarse execution time accounting
or incorrect parameter assignment.
Notification takes the form of a
.B SIGXCPU
signal which is generated on each overrun.
+.IP
+This
+.BR SIGXCPU
+signal is
+.I process-directed
+(see
+.BR signal (7))
+rather than thread-directed.
+This is probably a bug.
+On the one hand,
+.BR sched_setattr ()
+is being used to set a per-thread attribute.
+On the other hand, if the process-directed signal is delivered to
+a thread inside the process other than the one that had a run-time overrun,
+the application has no way of knowing which thread overran.
.RE
.TP
.I sched_nice