From: Leo Liang <ycliang@andestech.com>
To: <chengming.zhou@linux.dev>
Cc: <mingo@redhat.com>, <peterz@infradead.org>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
<bsegall@google.com>, <mgorman@suse.de>, <bristot@redhat.com>,
<vschneid@redhat.com>, <zhouchengming@bytedance.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] sched/fair: Fix cfs_rq_is_decayed() on !SMP
Date: Mon, 21 Aug 2023 09:29:58 +0800 [thread overview]
Message-ID: <ZOK92_xLVsMmIEDE@swlinux02> (raw)
In-Reply-To: <20230818132148.2237811-1-chengming.zhou@linux.dev>
Hi Chengming,
On Fri, Aug 18, 2023 at 09:21:48PM +0800, chengming.zhou@linux.dev wrote:
> From: Chengming Zhou <zhouchengming@bytedance.com>
>
> We don't need to maintain per-queue leaf_cfs_rq_list on !SMP, since
> it's used for cfs_rq load tracking & balance on SMP.
>
> But sched debug interface use it to print per-cfs_rq stats, which
> maybe better to change to use walk_tg_tree_from() instead.
>
> This patch just fix the !SMP version cfs_rq_is_decayed(), so the
> per-queue leaf_cfs_rq_list is also maintained correctly on !SMP,
> to fix the warning in assert_list_leaf_cfs_rq().
>
> Fixes: 0a00a354644e ("sched/fair: Delete useless condition in tg_unthrottle_up()")
> Reported-by: Leo Liang <ycliang@andestech.com>
> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
> ---
> kernel/sched/fair.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks for the quick patch!
Tested-by: Leo Yu-Chi Liang <ycliang@andestech.com>
Best regards,
Leo
next prev parent reply other threads:[~2023-08-21 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 9:35 PROBLEM: LTP cfs_bandwidth01 test bumped into SCHED_WARN_ON after de-selecting CONFIG_SMP Leo Liang
2023-08-18 11:35 ` [PATCH] sched/fair: Fix cfs_rq_is_decayed() on !SMP chengming.zhou
2023-08-18 12:25 ` Vincent Guittot
2023-08-18 13:17 ` Chengming Zhou
2023-08-18 13:21 ` [PATCH v2] " chengming.zhou
2023-08-21 1:29 ` Leo Liang [this message]
2023-08-21 11:59 ` Vincent Guittot
-- strict thread matches above, loose matches on Subject: below --
2023-09-13 13:20 chengming.zhou
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=ZOK92_xLVsMmIEDE@swlinux02 \
--to=ycliang@andestech.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=chengming.zhou@linux.dev \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=zhouchengming@bytedance.com \
/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