From: Peter Zijlstra <peterz@infradead.org>
To: Lin Ming <minggr@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: current->sched_class->yield_task is NULL, any hint?
Date: Wed, 9 Apr 2014 21:34:44 +0200 [thread overview]
Message-ID: <20140409193444.GA26782@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAF1ivSbVf0+PTzFdO+tNo33C6h6=HiBeKVF2jRvMQe=+RnPVxA@mail.gmail.com>
On Wed, Apr 09, 2014 at 11:49:17AM -0700, Lin Ming wrote:
> On Wed, Apr 9, 2014 at 11:32 AM, Lin Ming <minggr@gmail.com> wrote:
> > On Wed, Apr 9, 2014 at 11:25 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> >> On Wed, Apr 09, 2014 at 10:43:32AM -0700, Lin Ming wrote:
> >>> Hi Peter,
> >>>
> >>> I hit a panic in sys_sched_yield() because(for some unknown reason)
> >>> current->sched_class->yield_task is NULL.
> >>> It's an ARM embedded board with 3.4-rt kernel.
> >>>
> >>> Could you share any hint for the possible causes?
> >>
> >> What class does current->sched_class point to?
> >
> > [12890.088232] Process swapper/0 (pid: 0, stack limit = 0xc07042f0)
> >
> > It's idle task. I think it should be idle_sched_class.
> > But let me double check it.
>
> idle_sched_class has no "yield_task" defined.
> Does it mean that idle task should not call yield() at all?
Indeed. The idle task should never call yield. In fact, it should only
ever run the idle loop code, and that had better bloody not include a
yield call.
next prev parent reply other threads:[~2014-04-09 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 17:43 Lin Ming
2014-04-09 18:25 ` Peter Zijlstra
2014-04-09 18:32 ` Lin Ming
2014-04-09 18:49 ` Lin Ming
2014-04-09 19:34 ` Peter Zijlstra [this message]
2014-04-09 19:47 ` Peter Zijlstra
2014-04-09 20:08 ` Peter Zijlstra
2014-04-09 21:39 ` Lin Ming
2014-04-19 16:21 ` Paul Gortmaker
2014-04-19 16:58 ` Lin Ming
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=20140409193444.GA26782@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minggr@gmail.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
Powered by JetHome