From: Peter Zijlstra <peterz@infradead.org>
To: "Kuyo Chang (張建文)" <Kuyo.Chang@mediatek.com>
Cc: "dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
wsd_upstream <wsd_upstream@mediatek.com>,
"vschneid@redhat.com" <vschneid@redhat.com>,
"bristot@redhat.com" <bristot@redhat.com>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"bsegall@google.com" <bsegall@google.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH] sched: Fix stop_one_cpu_nowait() vs hotplug
Date: Wed, 11 Oct 2023 15:26:26 +0200 [thread overview]
Message-ID: <20231011132626.GP14330@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <172a3c89d7937725b61721e869eab3e5ae582643.camel@mediatek.com>
On Wed, Oct 11, 2023 at 03:24:19AM +0000, Kuyo Chang (張建文) wrote:
> On Tue, 2023-10-10 at 22:04 +0200, Peter Zijlstra wrote:
> >
> > External email : Please do not click links or open attachments until
> > you have verified the sender or the content.
> > On Tue, Oct 10, 2023 at 04:57:47PM +0200, Peter Zijlstra wrote:
> > > On Tue, Oct 10, 2023 at 02:40:22PM +0000, Kuyo Chang (張建文) wrote:
> >
> > > > It is running good so far(more than a week)on hotplug/set
> > affinity
> > > > stress test. I will keep it testing and report back if it happens
> > > > again.
> > >
> > > OK, I suppose I should look at writing a coherent Changelog for
> > this
> > > then...
> >
> > Something like the below... ?
> >
> Thanks for illustrate the race scenario. It looks good to me.
> But how about RT? Does RT also need this invocations as below?
>
> ---
> kernel/sched/rt.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index e93b69ef919b..6aaf0a3d6081 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -2063,9 +2063,11 @@ static int push_rt_task(struct rq *rq, bool
> pull)
> */
> push_task = get_push_task(rq);
> if (push_task) {
> + preempt_disable();
> raw_spin_rq_unlock(rq);
> stop_one_cpu_nowait(rq->cpu, push_cpu_stop,
> push_task, &rq->push_work);
> + preempt_enable();
> raw_spin_rq_lock(rq);
> }
>
> @@ -2402,9 +2404,11 @@ static void pull_rt_task(struct rq *this_rq)
> double_unlock_balance(this_rq, src_rq);
>
> if (push_task) {
> + preempt_disable();
> raw_spin_rq_unlock(this_rq);
> stop_one_cpu_nowait(src_rq->cpu, push_cpu_stop,
> push_task, &src_rq-
> >push_work);
> + preempt_enable();
> raw_spin_rq_lock(this_rq);
> }
> }
bah, clearly git-grep didn't work for me last night, I'll go fix up.
next prev parent reply other threads:[~2023-10-11 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 3:34 [PATCH 1/1] sched/core: Fix stuck on completion for affine_move_task() when stopper disable Kuyo Chang
2023-09-27 8:08 ` Peter Zijlstra
2023-09-27 15:57 ` Kuyo Chang (張建文)
2023-09-28 15:16 ` Peter Zijlstra
2023-09-28 15:19 ` Peter Zijlstra
2023-09-29 10:21 ` Peter Zijlstra
2023-10-01 15:15 ` Kuyo Chang (張建文)
2023-10-10 14:40 ` Kuyo Chang (張建文)
2023-10-10 14:57 ` Peter Zijlstra
2023-10-10 20:04 ` [PATCH] sched: Fix stop_one_cpu_nowait() vs hotplug Peter Zijlstra
2023-10-11 3:24 ` Kuyo Chang (張建文)
2023-10-11 13:26 ` Peter Zijlstra [this message]
2023-10-13 8:06 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
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=20231011132626.GP14330@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Kuyo.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wsd_upstream@mediatek.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