[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240813144348.1180344-3-christian.loehle@arm.com>
Date: Tue, 13 Aug 2024 15:43:46 +0100
From: Christian Loehle <christian.loehle@....com>
To: linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org,
rafael@...nel.org
Cc: vincent.guittot@...aro.org,
qyousef@...alina.io,
peterz@...radead.org,
daniel.lezcano@...aro.org,
rostedt@...dmis.org,
juri.lelli@...hat.com,
dietmar.eggemann@....com,
Christian Loehle <christian.loehle@....com>
Subject: [PATCH 2/4] sched/deadline: Clarify nanoseconds in uapi
Specify the time values of the deadline parameters of deadline,
runtime, and period as being in nanoseconds explicitly as they always
have been.
Signed-off-by: Christian Loehle <christian.loehle@....com>
---
include/uapi/linux/sched/types.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/uapi/linux/sched/types.h b/include/uapi/linux/sched/types.h
index 90662385689b..bf6e9ae031c1 100644
--- a/include/uapi/linux/sched/types.h
+++ b/include/uapi/linux/sched/types.h
@@ -58,9 +58,9 @@
*
* This is reflected by the following fields of the sched_attr structure:
*
- * @sched_deadline representative of the task's deadline
- * @sched_runtime representative of the task's runtime
- * @sched_period representative of the task's period
+ * @sched_deadline representative of the task's deadline in nanoseconds
+ * @sched_runtime representative of the task's runtime in nanoseconds
+ * @sched_period representative of the task's period in nanoseconds
*
* Given this task model, there are a multiplicity of scheduling algorithms
* and policies, that can be used to ensure all the tasks will make their
--
2.34.1
Powered by blists - more mailing lists