public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"dave@stgolabs.net" <dave@stgolabs.net>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>,
	"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
	"Ivanov, Petr" <petr.ivanov@siemens.com>
Subject: Re: [PATCH v2][5.10, 5.15, 6.1][1/1] hrtimer: Ignore slack time for RT tasks in schedule_hrtimeout_range()
Date: Tue, 20 Feb 2024 14:49:00 +0000	[thread overview]
Message-ID: <89eef284bd0fb1f60dbfc62decd2a0438d436c6e.camel@siemens.com> (raw)
In-Reply-To: <2024022057-slit-herself-a4d8@gregkh>

On Tue, 2024-02-20 at 15:32 +0100, Greg KH wrote:
> On Tue, Feb 20, 2024 at 01:34:03PM +0100, Felix Moessbauer wrote:
> > From: Davidlohr Bueso <dave@stgolabs.net>
> > 
> > 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
> 
> You can't forward on a patch without signing off on it as well :(

Ok, thanks for the info. I'll add the signoff and send a v3.

> 
> And this is already in the 6.1.53 release, why apply it again?

I can't find it there and also the change is not included in linux-
6.1.y or 6.1.53. There is another commit referencing this patch (linux-
6.1.y, fd4d61f85e7625cb21a7eff4efa1de46503ed2c3), but the "hrtimer:
Ignore slack time ..." patch did not get backported so far.
I also checked the source of v6.1.y and could not find the related
change. Which commit exactly are you referring to?

Felix

> 
> confused,
> 
> greg k-h

-- 
Siemens AG, Technology
Linux Expert Center



  reply	other threads:[~2024-02-20 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 12:34 [PATCH v2][5.10, 5.15, 6.1][0/1] hrtimer: Ignore slack time for RT tasks Felix Moessbauer
2024-02-20 12:34 ` [PATCH v2][5.10, 5.15, 6.1][1/1] hrtimer: Ignore slack time for RT tasks in schedule_hrtimeout_range() Felix Moessbauer
2024-02-20 14:32   ` Greg KH
2024-02-20 14:49     ` MOESSBAUER, Felix [this message]
2024-02-20 14:58       ` gregkh

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=89eef284bd0fb1f60dbfc62decd2a0438d436c6e.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=bigeasy@linutronix.de \
    --cc=dave@stgolabs.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jan.kiszka@siemens.com \
    --cc=petr.ivanov@siemens.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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