From: Robert Love <rml@ufl.edu>
To: Todd Inglett <tinglett@magnaspeed.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sched_init prematurely enables interrupts
Date: 12 Feb 2003 11:02:07 -0500 [thread overview]
Message-ID: <1045065727.4234.7.camel@phantasy> (raw)
In-Reply-To: <3E4A4FD8.6070203@magnaspeed.net>
On Wed, 2003-02-12 at 08:44, Todd Inglett wrote:
> The problem is that wake_up_forked_process() does an rq_unlock(rq) which
> is a spin_unlock_irq.
I believe this is fixed in Linus's bitkeeper.
Robert Love
prev parent reply other threads:[~2003-02-12 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 13:44 sched_init prematurely enables interrupts Todd Inglett
2003-02-12 16:02 ` Robert Love [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=1045065727.4234.7.camel@phantasy \
--to=rml@ufl.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tinglett@magnaspeed.net \
/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