From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Cc: kpreempt-tech@lists.sourceforge.net
Subject: [patch] 2.4: updated preemptable kernel
Date: 09 Sep 2002 20:22:30 -0400 [thread overview]
Message-ID: <1031617351.949.6.camel@phantasy> (raw)
Updated fully preemptive kernel patches are available at:
2.4.19: http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.19-2.patch
2.4.20-pre5: http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.20-pre5-1.patch
2.4.20-pre5-ac4: http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.20-pre5-ac4-1.patch
and your favorite mirrors.
These releases contain some of the recent fixes from 2.5. Note new
design features of kernel preemption will most likely not be back-ported
from 2.5; just fixes to the existing infrastructure.
The above patches include fixes for the "preempting with interrupts
disabled" bug as well as some other misc. issues. Note they are not per
se in sync with 2.5 or each other yet...
Enjoy,
Robert Love
reply other threads:[~2002-09-10 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1031617351.949.6.camel@phantasy \
--to=rml@tech9.net \
--cc=kpreempt-tech@lists.sourceforge.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