All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] (Updated) Preemptible Kernel
Date: 01 Oct 2001 00:21:44 -0400	[thread overview]
Message-ID: <1001910106.888.12.camel@phantasy> (raw)

Updated patches for 2.4.10, 2.4.11-pre1, and 2.4.10-ac1 are at
http://tech9.net/rml/linux

Note that the 2.4.10 patch is updated over previous patches.

It's been awhile, because a lot has changed.  Please give this a good
once (and twice) -over.  For those of you using preempt-stats, I suggest
not keeping that patch compiled in during regular use and certainly not
during any benchmarking.

What's New:

Most notably, George Anzinger of MontaVista rewrote how we keep track of
whether a task is preempted or not.  The "preempt bit" has been moved
from a task's status flag to the preempt_count (per-task_struct)
variable.  The resulting code is cleaner and simpler, and as a bonus the
race with ptrace and signals (and any undetected similar problems) has
been fixed, so we don't need explicit fixes.

I also renamed our namespace, cleaning things up, and trying to stick to
a prefix of "preempt."  Most important, ctx_sw_on and ctx_sw_off are now
preempt_enable and preempt_disable.

The ChangeLog since the last official release:

20010928
- have spin_lock_prefetch prefetch the preempt_count, too,
  since its incremented on each spin_lock
- some more ifdef and namespace cleanups

20010925
- modify our handling of the "preemption bit": move from the
  task's status to the preempt_count
- the above removes the risk of race in ptrace and SIGSTOP
  signal handling, so we can back out those fixes.
- rearrange our namespace.  most notably, ctx_sw_on/off
  is now preempt_enable/disable.
- cleanup some defines

20010923
- fix strace race: make ptrace preempt safe
- fix job control race: make SIGSTOP signal preempt
  safe
- fix adfs compile bug: add sched.h include to
  fs/adfs/map.c

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


             reply	other threads:[~2001-10-01  4:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01  4:21 Robert Love [this message]
2001-10-01  5:34 ` [PATCH] (Updated) Preemptible Kernel Steve Kieu
2001-10-01  5:46   ` Robert Love
  -- strict thread matches above, loose matches on Subject: below --
2001-09-19  0:10 Robert Love
2001-09-19  7:18 ` Robert Love
2001-09-09 22:38 Robert Love
2001-09-06 22:02 Robert Love
2001-09-06 20:39 ` Phillip Susi
2001-09-07  0:58   ` Robert Love
2001-09-07  1:10   ` Daniel Phillips
2001-09-09  4:44 ` 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=1001910106.888.12.camel@phantasy \
    --to=rml@tech9.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 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.