From: Valentin Schneider <valentin.schneider@arm.com>
To: paulmck@kernel.org
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@kernel.org, tglx@linutronix.de, jiangshanlai@gmail.com,
cai@redhat.com, vincent.donnefort@arm.com, decui@microsoft.com,
vincent.guittot@linaro.org, rostedt@goodmis.org, tj@kernel.org
Subject: Re: [PATCH] sched/core: Print out straggler tasks in sched_cpu_dying()
Date: Thu, 14 Jan 2021 10:37:35 +0000 [thread overview]
Message-ID: <jhjczy7ztw0.mognet@arm.com> (raw)
In-Reply-To: <20210114003613.GD2743@paulmck-ThinkPad-P72>
On 13/01/21 16:36, Paul E. McKenney wrote:
> On Thu, Jan 14, 2021 at 12:15:24AM +0000, Valentin Schneider wrote:
>> On 13/01/21 14:02, Paul E. McKenney wrote:
>> Thanks for giving it a spin! I think with the current series (either
>> Lai's or Peter's) sched_cpu_dying() should go smoothly, but you never
>> know.
>
> I was running the patch set having one of Lai's and three of Peter's,
> which sounds like Peter's.
That's how I was seeing it :)
> If I understand which series is which,
> Peter's has the advantage of not requiring rcutorture changes. ;-)
>
>> > However, it did produce the following new-to-me splat, which will
>> > hopefully be of some help.
>> >
>> > Thanx, Paul
>> >
>> > ------------------------------------------------------------------------
>> >
>> > WARNING: CPU: 2 PID: 23 at kernel/kthread.c:508 kthread_set_per_cpu+0x3b/0x50
>>
>> Aha, so that's that warning I was expecting to see [1].
>> Did you also get the process_one_work() one?
>
> Yes. Of 112 one-hour runs, there were five process_one_work() splats
> and two kthread_set_per_cpu() splats. Each splat-ridden run had exactly
> one splat.
>
I was expecting to see both in one run, so am still somewhat confused.
next prev parent reply other threads:[~2021-01-14 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 18:31 [PATCH] sched/core: Print out straggler tasks in sched_cpu_dying() Valentin Schneider
2021-01-13 22:02 ` Paul E. McKenney
2021-01-14 0:15 ` Valentin Schneider
2021-01-14 0:36 ` Paul E. McKenney
2021-01-14 10:37 ` Valentin Schneider [this message]
2021-01-14 15:22 ` Paul E. McKenney
2021-01-14 15:52 ` Valentin Schneider
2021-01-14 17:13 ` Paul E. McKenney
2021-01-15 16:54 ` Paul E. McKenney
2021-01-22 17:41 ` [tip: sched/urgent] " tip-bot2 for Valentin Schneider
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=jhjczy7ztw0.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=cai@redhat.com \
--cc=decui@microsoft.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vincent.donnefort@arm.com \
--cc=vincent.guittot@linaro.org \
/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