Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Janne Huttunen (Nokia)" <janne.huttunen@nokia.com>
Subject: Re: Please backport 101f3498b4bd to 6.18.y
Date: Sun, 26 Jul 2026 08:04:40 -0400	[thread overview]
Message-ID: <20260725192000.stable-0001@kernel.org> (raw)
In-Reply-To: <PAWPR07MB100712177EB29A65F4385E4C29ACF2@PAWPR07MB10071.eurprd07.prod.outlook.com>

> My attempt at a backport is below. Apologies in advance if the mail
> system mangles it. The only real diff between this and the original
> should be the use use of div_s64 vs div64_long + maybe tiny bit of
> patch context.

Thanks for putting this together, and for the weeks of production
testing.

I'd like to hold this one until Peter can weigh in. Upstream the revert
was preceded by 4823725d9d1d ("sched/fair: Increase weight bits for
avg_vruntime"), which is what actually cured the underlying rounding
artifact that 6d71a9c61604 was working around. That prerequisite is part
of the larger v7.1 avg_vruntime rework and isn't practical to bring back
to 6.18. Reverting alone on 6.18 (which still uses the scale_load_down
avg_vruntime) theoretically re-exposes that artifact, so I'd rather not
queue a scheduler change like this without the author's ack.

Peter, does a standalone revert of 6d71a9c61604 look correct/safe for
6.18 without 4823725d9d1d?

-- 
Thanks,
Sasha

      reply	other threads:[~2026-07-26 12:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  7:14 Please backport 101f3498b4bd to 6.18.y Janne Huttunen (Nokia)
2026-07-24 11:22 ` Sasha Levin
2026-07-24 12:58   ` Janne Huttunen (Nokia)
2026-07-26 12:04     ` 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=20260725192000.stable-0001@kernel.org \
    --to=sashal@kernel.org \
    --cc=janne.huttunen@nokia.com \
    --cc=peterz@infradead.org \
    --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