From: William Lee Irwin III <wli@holomorphy.com>
To: Miles Bader <miles@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WARN_ON noise in 2.5.63's kernel/sched.c:context_switch
Date: Tue, 4 Mar 2003 23:24:39 -0800 [thread overview]
Message-ID: <20030305072439.GQ1195@holomorphy.com> (raw)
In-Reply-To: <buok7fetheb.fsf@mcspd15.ucom.lsi.nec.co.jp>
On Wed, Mar 05, 2003 at 04:13:48PM +0900, Miles Bader wrote:
> Ok, I think I found the reason; sched.c cleans up some stuff in
> schedule_tail, and in this code (arch/v850/kernel/entry.S):
> C_ENTRY(ret_from_fork):
> #if defined(CONFIG_SMP) || defined(CONFIG_PREEMPT)
> mov r10, r6 // switch_thread returns the prev task.
> jarl CSYM(schedule_tail), lp // ...which is schedule_tail's arg
> #endif
> mov r0, r10 // Child's fork call should return 0.
> br ret_from_trap // Do normal trap return.
> ... it only calls that if CONFIG_PREEMPT is turned on. If I remove the
> #ifdef, then I get no warnings.
> I take it that the call to schedule_tail should now be unconditional?
> [some other archs have the same #ifdef]
Yeah, this is the root problem. You have to go through schedule_tail()
to clean up the mm's etc.
-- wli
prev parent reply other threads:[~2003-03-05 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 6:35 Miles Bader
2003-02-25 6:37 ` William Lee Irwin III
2003-03-05 7:13 ` Miles Bader
2003-03-05 7:24 ` William Lee Irwin III [this message]
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=20030305072439.GQ1195@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.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
all inboxes | Powered by JetHome®