From: Thomas Gleixner <tglx@linutronix.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>, stable@vger.kernel.org
Cc: dave@stgolabs.net, bigeasy@linutronix.de,
petr.ivanov@siemens.com, jan.kiszka@siemens.com
Subject: Re: [PATCH][5.10, 5.15, 6.1][1/1] hrtimer: Ignore slack time for RT tasks in schedule_hrtimeout_range()
Date: Mon, 19 Feb 2024 12:21:03 +0100 [thread overview]
Message-ID: <87sf1oaee8.ffs@tglx> (raw)
In-Reply-To: <20240219080851.27386-2-felix.moessbauer@siemens.com>
On Mon, Feb 19 2024 at 09:08, Felix Moessbauer wrote:
> From: Davidlohr Bueso <dave@stgolabs.net>
This lacks a reference to the upstream commit.
Commit 0c52310f260014d95c1310364379772cb74cf82d upstream.
> While in theory the timer can be triggered before expires + delta, for the
> cases of RT tasks they really have no business giving any lenience for
> extra slack time, so override any passed value by the user and always use
> zero for schedule_hrtimeout_range() calls. Furthermore, this is similar to
> what the nanosleep(2) family already does with current->timer_slack_ns.
>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Link: https://lore.kernel.org/r/20230123173206.6764-3-dave@stgolabs.net
next prev parent reply other threads:[~2024-02-19 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 8:08 [PATCH][5.10, 5.15, 6.1][0/1] hrtimer: Ignore slack time for RT tasks Felix Moessbauer
2024-02-19 8:08 ` [PATCH][5.10, 5.15, 6.1][1/1] hrtimer: Ignore slack time for RT tasks in schedule_hrtimeout_range() Felix Moessbauer
2024-02-19 11:21 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 17:11 [PATCH][5.10, 5.15, 6.1][0/1] hrtimer: Ignore slack time for RT tasks Felix Moessbauer
2024-02-16 17:11 ` [PATCH][5.10, 5.15, 6.1][1/1] hrtimer: Ignore slack time for RT tasks in schedule_hrtimeout_range() Felix Moessbauer
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=87sf1oaee8.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=petr.ivanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.