public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Aboorva Devarajan <aboorvad@linux.ibm.com>
Cc: void@manifault.com, linux-kernel@vger.kernel.org
Subject: Re: [sched_ext/for-6.11]: Issue with BPF Scheduler during CPU Hotplug
Date: Mon, 26 Aug 2024 08:32:03 -1000	[thread overview]
Message-ID: <ZszKI2GA-8yparh_@slm.duckdns.org> (raw)
In-Reply-To: <3da12c96daecaa055c478816f5e86c7b44a04d53.camel@linux.ibm.com>

Hello,

On Fri, Aug 23, 2024 at 02:50:01PM +0530, Aboorva Devarajan wrote:
...
> I applied this patch to the almost latest sched-ext (for-6.12) branch upto
> commit 89909296a51e792 ("sched_ext: Don't use double locking to migrate
> tasks across CPUs") and let the test run for over 20 hours, and it completed
> without any hangs on both x86 and PowerPC.
> 
> So, indeed, making sure that both scx_fork_rwsem and cpu_hotplug_lock (read)
> are only held together simulataneously when they can both be acquired seems
> to be resolving the deadlock.

Thanks a lot for confirming. Let me think it over a bit re. what should be
applied.

Thanks.

-- 
tejun

  reply	other threads:[~2024-08-26 18:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  7:51 [sched_ext/for-6.11]: Issue with BPF Scheduler during CPU Hotplug Aboorva Devarajan
2024-07-10  0:02 ` Tejun Heo
2024-07-11 12:00   ` Aboorva Devarajan
2024-07-12 10:04     ` Aboorva Devarajan
2024-08-02 21:20       ` Tejun Heo
2024-08-10 18:24         ` Aboorva Devarajan
2024-08-13 19:54           ` Tejun Heo
2024-08-20  7:03             ` Aboorva Devarajan
2024-08-20 19:38               ` Tejun Heo
2024-08-23  9:20                 ` Aboorva Devarajan
2024-08-26 18:32                   ` Tejun Heo [this message]
2024-09-17 12:48                     ` Tejun Heo
2024-09-23 14:56                       ` Aboorva Devarajan
2024-09-23 18:21                         ` Tejun Heo
2024-09-24  8:03                           ` Alexei Starovoitov
2024-09-24 12:00                             ` Aboorva Devarajan
2024-09-24 16:57                               ` Song Liu
2024-09-30  6:37                                 ` Hari Bathini

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=ZszKI2GA-8yparh_@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=aboorvad@linux.ibm.com \
    --cc=linux-kernel@vger.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