From: "tip-bot2 for Christian Loehle" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Christian Loehle <christian.loehle@arm.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] cpufreq/cppc: Use NSEC_PER_MSEC for deadline task
Date: Wed, 11 Sep 2024 09:32:57 -0000 [thread overview]
Message-ID: <172604717704.2215.15463514490818312946.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240813144348.1180344-4-christian.loehle@arm.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 4eb71e3b4550593d9a862cc0aa754fad98679783
Gitweb: https://git.kernel.org/tip/4eb71e3b4550593d9a862cc0aa754fad98679783
Author: Christian Loehle <christian.loehle@arm.com>
AuthorDate: Tue, 13 Aug 2024 15:43:47 +01:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Wed, 11 Sep 2024 11:25:10 +02:00
cpufreq/cppc: Use NSEC_PER_MSEC for deadline task
Convert the cppc deadline task attributes to use the available
definitions to make them more readable.
No functional change.
Signed-off-by: Christian Loehle <christian.loehle@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Juri Lelli <juri.lelli@redhat.com>
Acked-by: Rafael J. Wysocki <rafael@kernel.org>
Link: https://lore.kernel.org/r/20240813144348.1180344-4-christian.loehle@arm.com
---
drivers/cpufreq/cppc_cpufreq.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/cpufreq/cppc_cpufreq.c b/drivers/cpufreq/cppc_cpufreq.c
index bafa32d..1a5ad18 100644
--- a/drivers/cpufreq/cppc_cpufreq.c
+++ b/drivers/cpufreq/cppc_cpufreq.c
@@ -224,9 +224,9 @@ static void __init cppc_freq_invariance_init(void)
* Fake (unused) bandwidth; workaround to "fix"
* priority inheritance.
*/
- .sched_runtime = 1000000,
- .sched_deadline = 10000000,
- .sched_period = 10000000,
+ .sched_runtime = NSEC_PER_MSEC,
+ .sched_deadline = 10 * NSEC_PER_MSEC,
+ .sched_period = 10 * NSEC_PER_MSEC,
};
int ret;
next prev parent reply other threads:[~2024-09-11 9:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 14:43 [PATCH 0/4] sched/deadline: nanoseconds clarifications Christian Loehle
2024-08-13 14:43 ` [PATCH 1/4] sched/deadline: Convert schedtool example to chrt Christian Loehle
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 2/4] sched/deadline: Clarify nanoseconds in uapi Christian Loehle
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 3/4] cpufreq/cppc: Use NSEC_PER_MSEC for deadline task Christian Loehle
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle [this message]
2024-08-13 14:43 ` [PATCH 4/4] sched/cpufreq: " Christian Loehle
2024-09-09 13:38 ` Vincent Guittot
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle
2024-08-13 16:02 ` [PATCH 0/4] sched/deadline: nanoseconds clarifications Juri Lelli
2024-09-09 13:01 ` Christian Loehle
2024-09-09 13:25 ` Peter Zijlstra
2024-09-09 16:39 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=172604717704.2215.15463514490818312946.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=christian.loehle@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®