From: Greg KH <gregkh@linuxfoundation.org>
To: wujing <realwujing@qq.com>
Cc: peterz@infradead.org, dongml2@chinatelecom.cn,
linux-kernel@vger.kernel.org, mingo@redhat.com,
yuanql9@chinatelecom.cn, stable@vger.kernel.org,
mengong8.dong@gmail.com
Subject: Re: Re: [PATCH] sched/fair: Correct CPU selection from isolated domain
Date: Tue, 30 Jul 2024 11:11:45 +0200 [thread overview]
Message-ID: <2024073032-ferret-obtrusive-3ce4@gregkh> (raw)
In-Reply-To: <tencent_0C989DE2631E74C23BA8B60EA234C4B2FA0A@qq.com>
On Tue, Jul 30, 2024 at 05:03:38PM +0800, wujing wrote:
> > If you're trying to backport something, I think you forgot to Cc stable
> > and provide the proper upstream commit.
> >
> > As is this isn't something I can do anything with. The patch does not
> > apply to any recent kernel and AFAICT this issue has long since been
> > fixed.
>
> When fixing this bug, I didn't pay much attention to upstream changes.
> Upon reviewing the history of relevant commits, I found that they have
> been merged and reverted multiple times:
>
> ```bash
> git log -S 'cpumask_test_cpu(cpu, sched_domain_span(sd))' --oneline \
> kernel/sched/fair.c
>
> 8aeaffef8c6e sched/fair: Take the scheduling domain into account in select_idle_smt()
> 3e6efe87cd5c sched/fair: Remove redundant check in select_idle_smt()
> 3e8c6c9aac42 sched/fair: Remove task_util from effective utilization in feec()
> c722f35b513f sched/fair: Bring back select_idle_smt(), but differently
> 6cd56ef1df39 sched/fair: Remove select_idle_smt()
> df3cb4ea1fb6 sched/fair: Fix wrong cpu selecting from isolated domain
> ```
>
> The latest upstream commit 8aeaffef8c6e is not applicable to linux-4.19.y.
> The current patch has been tested on linux-4.19.y and I am looking forward
> to its inclusion in the stable version.
What "current patch"?
confused,
greg k-h
next prev parent reply other threads:[~2024-07-30 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 7:10 [PATCH] sched/fair: Correct CPU selection from isolated domain wujing
2024-07-30 8:22 ` Peter Zijlstra
2024-07-30 9:03 ` wujing
2024-07-30 9:11 ` Greg KH [this message]
2024-07-30 9:25 ` wujing
2024-07-30 9:30 ` wujing
2024-07-30 9:41 ` Greg KH
2024-07-30 9:40 ` wujing
2024-07-30 9:51 ` Greg KH
2024-07-30 10:11 ` wujing
2024-07-30 10:20 ` Greg KH
2024-07-30 9:02 ` zhengzucheng
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=2024073032-ferret-obtrusive-3ce4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dongml2@chinatelecom.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mengong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=realwujing@qq.com \
--cc=stable@vger.kernel.org \
--cc=yuanql9@chinatelecom.cn \
/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