From: Andrea Righi <arighi@nvidia.com>
To: Changwoo Min <changwoo@igalia.com>
Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Fix lock imbalance in dispatch_to_local_dsq()
Date: Fri, 24 Jan 2025 07:21:04 +0100 [thread overview]
Message-ID: <Z5MxUBNheFBpNvZ_@gpd3> (raw)
In-Reply-To: <d26bdb31-53b2-4421-9ecd-8b1943a751d0@igalia.com>
On Fri, Jan 24, 2025 at 11:21:33AM +0900, Changwoo Min wrote:
> Hello Andrea,
>
> On 25. 1. 24. 08:42, Andrea Righi wrote:
> > kernel/sched/ext.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
> > index a24d48cebfb7..7500b1a26757 100644
> > --- a/kernel/sched/ext.c
> > +++ b/kernel/sched/ext.c
> > @@ -2617,6 +2617,8 @@ static void dispatch_to_local_dsq(struct rq *rq, struct scx_dispatch_q *dst_dsq,
> > /* if the destination CPU is idle, wake it up */
> > if (sched_class_above(p->sched_class, dst_rq->curr->sched_class))
> > resched_curr(dst_rq);
> > + } else {
> > + dst_rq = src_rq;
> > }
>
> The fix makes sense to me. Since this is a very specific and
> tricky case, it will be better to include detailed comments in
> the else part so anyone can easily understand why the else part
> is necessary.
Good idea, I'll send a v2 including a comment in the else part.
Thanks!
-Andrea
prev parent reply other threads:[~2025-01-24 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 23:42 [PATCH] sched_ext: Fix lock imbalance in dispatch_to_local_dsq() Andrea Righi
2025-01-24 2:21 ` Changwoo Min
2025-01-24 6:21 ` Andrea Righi [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=Z5MxUBNheFBpNvZ_@gpd3 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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