All of lore.kernel.org
 help / color / mirror / Atom feed
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.6.y 1/1] hrtimer: Use and report correct timerslack values for realtime tasks
Date: Thu, 13 Mar 2025 05:08:43 -0400	[thread overview]
Message-ID: <20250312233302-2946e29efda0cecc@stable.kernel.org> (raw)
In-Reply-To: <20250311134931.290856-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)

Note: The patch differs from the upstream commit:
---
1:  ed4fb6d7ef681 ! 1:  8ec8728ce513f 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);
      
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y        |  Success    |  Success   |

      reply	other threads:[~2025-03-13  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 13:49 [PATCH 6.6.y 1/1] hrtimer: Use and report correct timerslack values for realtime tasks Felix Moessbauer
2025-03-13  9:08 ` 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=20250312233302-2946e29efda0cecc@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 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.