From: Todd Inglett <tinglett@magnaspeed.net>
To: linux-kernel@vger.kernel.org
Subject: sched_init prematurely enables interrupts
Date: Wed, 12 Feb 2003 07:44:56 -0600 [thread overview]
Message-ID: <3E4A4FD8.6070203@magnaspeed.net> (raw)
I think this bit is prematurely enabling interrupts in sched_init:
======== kernel/sched.c 1.1..1.156 ========
D 1.156 03/02/09 21:32:34-08:00 torvalds@home.transmeta.com 179 178
32/24/2466
P kernel/sched.c
C Make "try_to_wake_up()" care about the state of the process woken up.
C
C This simplifies "default_wake_function()", and makes it possible for
C signal handling to wake up only stopped tasks without races.
C
C It also makes it impossible to wake up already running processes, which
C means that the early boot sequence has to use the (much more correct)
C "wake_up_forked_process()" to put the initial task on the runqueues.
The problem is that wake_up_forked_process() does an rq_unlock(rq) which
is a spin_unlock_irq.
-todd
next reply other threads:[~2003-02-12 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 13:44 Todd Inglett [this message]
2003-02-12 16:02 ` sched_init prematurely enables interrupts Robert Love
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=3E4A4FD8.6070203@magnaspeed.net \
--to=tinglett@magnaspeed.net \
--cc=linux-kernel@vger.kernel.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