From: yangyingliang@huaweicloud.com
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
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, tglx@linutronix.de, yu.c.chen@intel.com,
tim.c.chen@linux.intel.com, yangyingliang@huawei.com,
liwei391@huawei.com
Subject: Re: [PATCH resend] sched/smt: fix unbalance sched_smt_present dec/inc
Date: Tue, 2 Jul 2024 19:38:37 +0800 (GMT+08:00) [thread overview]
Message-ID: <5fce12a8.c23.190733d53e9.Coremail.yangyingliang@huaweicloud.com> (raw)
In-Reply-To: <20240702084418.GB11386@noisy.programming.kicks-ass.net>
> -----Original Messages-----
> From: "Peter Zijlstra" <peterz@infradead.org>
> Sent Time: 2024-07-02 16:44:18 (Tuesday)
> To: "Yang Yingliang" <yangyingliang@huaweicloud.com>
> Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, 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, tglx@linutronix.de, yu.c.chen@intel.com, tim.c.chen@linux.intel.com, yangyingliang@huawei.com, liwei391@huawei.com
> Subject: Re: [PATCH resend] sched/smt: fix unbalance sched_smt_present dec/inc
>
> On Tue, Jul 02, 2024 at 04:11:28PM +0800, Yang Yingliang wrote:
> > From: Yang Yingliang <yangyingliang@huawei.com>
> >
> > I got the following warn report while doing stress test:
> >
> > jump label: negative count!
> > WARNING: CPU: 3 PID: 38 at kernel/jump_label.c:263 static_key_slow_try_dec+0x9d/0xb0
> > Call Trace:
> > <task>
> > __static_key_slow_dec_cpuslocked+0x16/0x70
> > sched_cpu_deactivate+0x26e/0x2a0
> > cpuhp_invoke_callback+0x3ad/0x10d0
> > cpuhp_thread_fun+0x3f5/0x680
> > smpboot_thread_fn+0x56d/0x8d0
> > kthread+0x309/0x400
> > ret_from_fork+0x41/0x70
> > ret_from_fork_asm+0x1b/0x30
> > </task>
> >
> > Because when cpuset_cpu_inactive() fails in sched_cpu_deactivate(),
> > the cpu offline failed, but sched_smt_present is decremented before
> > calling sched_cpu_deactivate(), it leads to unbalanced dec/inc, so
> > fix it by incrementing sched_smt_present in the error path.
> >
> > Fixes: c5511d03ec09 ("sched/smt: Make sched_smt_present track topology")
> > Reviewed-by: Chen Yu <yu.c.chen@intel.com>
> > Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>
> > Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> > ---
> > kernel/sched/core.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index bcf2c4cc0522..5ab6717b57e0 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -9756,6 +9756,10 @@ int sched_cpu_deactivate(unsigned int cpu)
> > sched_update_numa(cpu, false);
> > ret = cpuset_cpu_inactive(cpu);
> > if (ret) {
> > +#ifdef CONFIG_SCHED_SMT
> > + if (cpumask_weight(cpu_smt_mask(cpu)) == 2)
> > + static_branch_inc_cpuslocked(&sched_smt_present);
> > +#endif
> > balance_push_set(cpu, false);
> > set_cpu_active(cpu, true);
> > sched_update_numa(cpu, true);
>
> Yes, does indeed appear needed, however!, when I look at
> what else goes before this failure, should we not also call
> set_rq_online() and things like that?
Yes, set_rq_online() is needed in the error path. I will send a new patch to add this.
>
> That is, can we rework things to be less fragile by sharing code between
> this error path and sched_cpu_activate() ?
</yangyingliang@huawei.com></tim.c.chen@linux.intel.com></yu.c.chen@intel.com></yangyingliang@huawei.com></yangyingliang@huaweicloud.com></peterz@infradead.org>
prev parent reply other threads:[~2024-07-02 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 8:11 Yang Yingliang
2024-07-02 8:44 ` Peter Zijlstra
2024-07-02 11:38 ` yangyingliang [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=5fce12a8.c23.190733d53e9.Coremail.yangyingliang@huaweicloud.com \
--to=yangyingliang@huaweicloud.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yangyingliang@huawei.com \
--cc=yu.c.chen@intel.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
all inboxes | Powered by JetHome®