From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y 1/1] hrtimer: Use and report correct timerslack values for realtime tasks
Date: Thu, 13 Mar 2025 05:11:37 -0400 [thread overview]
Message-ID: <20250312203334-b3cc22061d84f853@stable.kernel.org> (raw)
In-Reply-To: <20250311140706.435615-1-felix.moessbauer@siemens.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: ed4fb6d7ef68111bb539283561953e5c6e9a6e38
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: ed4fb6d7ef681 ! 1: a4d3916d07d4c hrtimer: Use and report correct timerslack values for realtime tasks
@@ Metadata
## Commit message ##
hrtimer: Use and report correct timerslack values for realtime tasks
+ commit ed4fb6d7ef68111bb539283561953e5c6e9a6e38 upstream.
+
The timerslack_ns setting is used to specify how much the hardware
timers should be delayed, to potentially dispatch multiple timers in a
single interrupt. This is a performance optimization. Timers of
@@ fs/select.c: u64 select_estimate_accuracy(struct timespec64 *tv)
}
- ## kernel/sched/syscalls.c ##
-@@ kernel/sched/syscalls.c: static void __setscheduler_params(struct task_struct *p,
+ ## kernel/sched/core.c ##
+@@ kernel/sched/core.c: static void __setscheduler_params(struct task_struct *p,
else if (fair_policy(policy))
p->static_prio = NICE_TO_PRIO(attr->sched_nice);
@@ kernel/time/hrtimer.c: long hrtimer_nanosleep(ktime_t rqtp, const enum hrtimer_m
- u64 slack;
-
- slack = current->timer_slack_ns;
-- if (rt_task(current))
+- if (dl_task(current) || rt_task(current))
- slack = 0;
hrtimer_init_sleeper_on_stack(&t, clockid, mode);
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-03-13 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 14:07 [PATCH 6.1.y 1/1] hrtimer: Use and report correct timerslack values for realtime tasks Felix Moessbauer
2025-03-13 9:11 ` Sasha Levin [this message]
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=20250312203334-b3cc22061d84f853@stable.kernel.org \
--to=sashal@kernel.org \
--cc=felix.moessbauer@siemens.com \
--cc=stable@vger.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