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: Tue, 13 Aug 2024 09:54:37 -1000 [thread overview]
Message-ID: <Zru5_UmEmWhNaPyo@slm.duckdns.org> (raw)
In-Reply-To: <e3069da05fb1676f8faad88b9a4dfc4a6cef4175.camel@linux.ibm.com>
Hello,
On Sat, Aug 10, 2024 at 11:54:24PM +0530, Aboorva Devarajan wrote:
...
> Sorry for the delayed response, I just got sometime on the machine to
> run this test.
>
> I applied the patchset on the latest sched-ext (for-next) branch and
> tested it, but the issue still persists. I did the test on a PowerPC
> system, as it is easier to reproduce the issue there compared to x86.
Bummer.
...
> I'll see if I can collect more details, and if there's anything else
> you'd want me check, please let me know.
Can you trigger sysrq-t when the system is stuck? Also, can you see whether
the problem is reproducible on x86 w/ the wq changes applied?
Thanks.
--
tejun
next prev parent reply other threads:[~2024-08-13 19:54 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 [this message]
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
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=Zru5_UmEmWhNaPyo@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