From: Robert Love <rml@tech9.net>
To: ultralinux@vger.kernel.org
Subject: Re: 2.5.5 on Sparc, Ughh...
Date: Thu, 21 Feb 2002 16:52:08 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-101431036622004@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-101422154814029@msgid-missing>
On Thu, 2002-02-21 at 03:04, george anzinger wrote:
> Uh, Dave, could you expound a bit on why you need a preemption lock
> around the notify parent/ schedule code? We have not found this to be
> needed on other archs, but maybe we missed something.
2.5 has diverged from the "patch" version of the code. We removed the
PREEMPT_ACTIVE flag and thus have a race against parent/wake up. All
arches disable preemption there.
Robert Love
next prev parent reply other threads:[~2002-02-21 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 16:12 2.5.5 on Sparc, Ughh Holzrichter, Bruce
2002-02-20 16:39 ` David S. Miller
2002-02-20 19:27 ` Holzrichter, Bruce
2002-02-21 8:04 ` george anzinger
2002-02-21 16:52 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 16:12 Holzrichter, Bruce
2002-02-20 16:39 ` David S. Miller
2002-02-21 8:04 ` george anzinger
2002-02-21 16:52 ` Robert Love
2002-02-20 19:27 Holzrichter, Bruce
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=marc-linux-ultrasparc-101431036622004@msgid-missing \
--to=rml@tech9.net \
--cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.