From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Peter Zijlstra <peterz@infradead.org>, Aaron Lu <ziqianlu@bytedance.com>
Cc: <mingo@kernel.org>, <linux-kernel@vger.kernel.org>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
<bsegall@google.com>, <mgorman@suse.de>, <vschneid@redhat.com>,
<tj@kernel.org>, <williams@redhat.com>, <jkacur@redhat.com>
Subject: Re: [PATCH 0/2] sched: Remove sched_class::balance()
Date: Thu, 20 Aug 2026 22:45:03 +0530 [thread overview]
Message-ID: <3898f82d-e48a-48d5-a13d-54fa5387a203@amd.com> (raw)
In-Reply-To: <20260820154052.GB4120091@noisy.programming.kicks-ass.net>
On 8/20/2026 9:10 PM, Peter Zijlstra wrote:
> On Thu, Jul 02, 2026 at 07:49:19PM +0800, Aaron Lu wrote:
>
>> The test caused a panic with below msg:
>
> What test do you run? I think all I have is the prctl selftest thing.
Stuff that goes sideways generally shows up with:
coresched new -t pid -- perf bench sched messaging -p -l 100000 -g 8
I generally consider a full run without any splats as a pass.
Performance tends to vary quite a bit depending upon number of groups.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-08-20 17:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 12:13 [PATCH 0/2] sched: Remove sched_class::balance() Peter Zijlstra
2026-06-24 12:13 ` [PATCH 1/2] sched/core: Allow newidle for core-sched Peter Zijlstra
2026-06-24 23:56 ` K Prateek Nayak
2026-06-25 12:41 ` Peter Zijlstra
2026-06-25 12:42 ` Peter Zijlstra
2026-06-24 12:13 ` [PATCH 2/2] sched: Remove sched_class::balance() Peter Zijlstra
2026-07-02 11:49 ` [PATCH 0/2] " Aaron Lu
2026-07-03 3:31 ` K Prateek Nayak
2026-08-19 9:39 ` Peter Zijlstra
2026-08-19 7:58 ` Peter Zijlstra
2026-08-19 14:36 ` Peter Zijlstra
2026-08-19 19:22 ` Tejun Heo
2026-08-20 7:18 ` Peter Zijlstra
2026-08-20 7:42 ` Tejun Heo
2026-08-20 7:58 ` Peter Zijlstra
2026-08-20 15:40 ` Peter Zijlstra
2026-08-20 17:15 ` K Prateek Nayak [this message]
2026-08-21 7:10 ` Peter Zijlstra
2026-08-21 2:44 ` Aaron Lu
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=3898f82d-e48a-48d5-a13d-54fa5387a203@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jkacur@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=williams@redhat.com \
--cc=ziqianlu@bytedance.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