From: Chris Mason <clm@meta.com>
To: Peter Zijlstra <peterz@infradead.org>, Rik van Riel <riel@surriel.com>
Cc: Pat Cody <pat@patcody.io>,
mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, linux-kernel@vger.kernel.org,
patcody@meta.com, kernel-team@meta.com, stable@vger.kernel.org,
Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] sched/fair: Add null pointer check to pick_next_entity()
Date: Mon, 14 Apr 2025 11:38:15 -0400 [thread overview]
Message-ID: <0049c6a0-8802-416c-9618-9d714c22af49@meta.com> (raw)
In-Reply-To: <20250414090823.GB5600@noisy.programming.kicks-ass.net>
On 4/14/25 5:08 AM, Peter Zijlstra wrote:
[ math and such ]
> The zero_vruntime patch I gave earlier should avoid this particular
> issue.
Here's a crash with the zero runtime patch. I'm trying to reproduce
this outside of prod so we can crank up the iteration speed a bit.
-chris
nr_running = 2
zero_vruntime = 19194347104893960
avg_vruntime = 6044054790
avg_load = 2
curr = {
cgroup urgent
vruntime = 24498183812106172
weight = 3561684 => 3478
rq = {
nr_running = 0
zero_vruntime = 505000008215941
avg_vruntime = 0
avg_load = 0
curr = {
cgroup urgent/-610604968056586240
vruntime = 505000008302509
weight = 455902 => 445
rq = {
nr_running = 0
zero_vruntime = 12234709899
avg_vruntime = 0
avg_load = 0
curr = {
task = 279047 (fc0)
vruntime = 12237278090
weight = 15360 => 15
}
tasks_timeline = [
]
}
}
tasks_timeline = [
]
}
}
tasks_timeline = [
{
cgroup optional
vruntime = 19194350126921355
weight = 1168 => 2
rq = {
nr_running = 2
zero_vruntime = 440280059357029
avg_vruntime = 476
avg_load = 688
tasks_timeline = [
{
cgroup optional/-610613050111295488
vruntime = 440280059333960
weight = 291271 => 284
rq = {
nr_running = 5
zero_vruntime = 65179829005
avg_vruntime = 0
avg_load = 75
tasks_timeline = [
{
task = 261672 (fc0)
vruntime = 65189926507
weight = 15360 => 15
},
{
task = 261332 (fc0)
vruntime = 65189480962
weight = 15360 => 15
},
{
task = 261329 (enc1:0:vp9_fbv)
vruntime = 65165843516
weight = 15360 => 15
},
{
task = 261334 (dec0:0:hevc_fbv)
vruntime = 65174065035
weight = 15360 => 15
},
{
task = 261868 (fc0)
vruntime = 65179829005
weight = 15360 => 15
},
]
}
},
{
cgroup optional/-610609318858457088
vruntime = 440280059373247
weight = 413911 => 404
rq = {
nr_running = 1
zero_vruntime = 22819875784
avg_vruntime = 0
avg_load = 15
tasks_timeline = [
{
task = 273291 (fc0)
vruntime = 22819875784
weight = 15360 => 15
},
]
}
},
]
}
},
]
next prev parent reply other threads:[~2025-04-14 15:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 20:53 Pat Cody
2025-03-20 22:42 ` Christian Loehle
2025-03-21 17:52 ` Pat Cody
2025-03-24 11:56 ` Peter Zijlstra
2025-03-25 15:12 ` Pat Cody
2025-03-25 18:59 ` Peter Zijlstra
2025-03-26 19:26 ` Pat Cody
2025-04-02 14:59 ` Rik van Riel
2025-04-02 18:07 ` Peter Zijlstra
2025-04-09 14:29 ` Rik van Riel
2025-04-09 15:27 ` Peter Zijlstra
2025-04-11 14:51 ` Rik van Riel
2025-04-14 9:08 ` Peter Zijlstra
2025-04-14 15:38 ` Chris Mason [this message]
2025-04-15 10:07 ` Peter Zijlstra
2025-04-16 7:59 ` Peter Zijlstra
[not found] ` <7B2CFC16-1ADE-4565-B555-7525A50494C2@surriel.com>
[not found] ` <20250402082221.GT5880@noisy.programming.kicks-ass.net>
2025-04-14 19:57 ` Rik van Riel
2025-04-15 8:02 ` Peter Zijlstra
2025-04-16 12:44 ` Peter Zijlstra
2025-04-16 14:19 ` Rik van Riel
2025-04-16 15:27 ` Chris Mason
2025-04-18 15:44 ` Peter Zijlstra
2025-04-18 23:49 ` Omar Sandoval
2025-04-22 0:06 ` Omar Sandoval
2025-04-22 14:13 ` Peter Zijlstra
2025-04-22 15:14 ` Peter Zijlstra
2025-04-25 8:53 ` Omar Sandoval
2025-04-22 13:36 ` Peter Zijlstra
2025-04-19 2:53 ` Mike Galbraith
[not found] <20250320173438.3562449-2-patcody@meta.com>
2025-03-24 15:56 ` Steven Rostedt
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=0049c6a0-8802-416c-9618-9d714c22af49@meta.com \
--to=clm@meta.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pat@patcody.io \
--cc=patcody@meta.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®