public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "qyousef@layalina.io" <qyousef@layalina.io>,
	"frederic@kernel.org" <frederic@kernel.org>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>,
	"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
	"anna-maria@linutronix.de" <anna-maria@linutronix.de>
Subject: Re: [PATCH v3 1/1] hrtimer: use and report correct timerslack values for realtime tasks
Date: Wed, 14 Aug 2024 12:42:27 +0200	[thread overview]
Message-ID: <8734n7per0.ffs@tglx> (raw)
In-Reply-To: <76cd1f3e07c6c12a7dceac31cdf7a3ca8d1e8265.camel@siemens.com>

On Tue, Aug 13 2024 at 10:23, Felix MOESSBAUER wrote:
> On Tue, 2024-08-13 at 11:45 +0200, Thomas Gleixner wrote:
>> Why are you declaring that a RT task has to have 0 slack if we are
>> lifting the hard coded slack zeroing in the hrtimer functions?
>
> This is what the manpage states [1]:
>
> + Timer slack is not applied to threads that are scheduled under a
> + real-time scheduling policy (see sched_setscheduler(2)).
>
> [1] https://man7.org/linux/man-pages/man2/PR_SET_TIMERSLACK.2const.html

Fair enough. Mention it in the changelog please.

Thanks,

        tglx

      reply	other threads:[~2024-08-14 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13  7:29 [PATCH v3 0/1] hrtimer: More fixes for handling of timer slack of rt tasks Felix Moessbauer
2024-08-13  7:29 ` [PATCH v3 1/1] hrtimer: use and report correct timerslack values for realtime tasks Felix Moessbauer
2024-08-13  9:45   ` Thomas Gleixner
2024-08-13 10:23     ` MOESSBAUER, Felix
2024-08-14 10:42       ` Thomas Gleixner [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=8734n7per0.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=anna-maria@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=frederic@kernel.org \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qyousef@layalina.io \
    /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