All of lore.kernel.org
 help / color / mirror / Atom feed
From: yodaiken@fsmlabs.com
To: yodaiken@fsmlabs.com, Robert Love <rml@tech9.net>,
	Mikael Pettersson <mikpe@csd.uu.se>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.18 Preempt Freezeups
Date: Fri, 15 Mar 2002 20:12:40 -0700	[thread overview]
Message-ID: <20020315201240.A7368@hq.fsmlabs.com> (raw)
In-Reply-To: <3C9153A7.292C320@ianduggan.net> <1016157250.4599.62.camel@phantasy> <3C91B2A1.48C74B82@ianduggan.net> <1016202310.908.1.camel@phantasy> <15506.7486.729120.64389@kim.it.uu.se> <1016219530.904.21.camel@phantasy> <20020315174036.A5068@hq.fsmlabs.com> <20020316014615.GE363@matchmail.com>
In-Reply-To: <20020316014615.GE363@matchmail.com>; from mfedyk@matchmail.com on Fri, Mar 15, 2002 at 05:46:15PM -0800

On Fri, Mar 15, 2002 at 05:46:15PM -0800, Mike Fedyk wrote:
> On Fri, Mar 15, 2002 at 05:40:36PM -0700, yodaiken@fsmlabs.com wrote:
> > On Fri, Mar 15, 2002 at 02:11:49PM -0500, Robert Love wrote:
> > > If you "poke the processor", to be SMP-safe, you should hold a lock to
> > > prevent multiple concurrent "pokings of the processor" - thus you become
> > > preempt-safe.
> > 
> > Without preempt:
> > 	x = movefrom processor register;
> >         do_something with x
> > 
> > is safe in SMP
> > With SMP it requires a lock.
> >
> 
> "With preempt it requires a lock" you mean?

Yep. Keyboard Operator error.


-- 
---------------------------------------------------------
Victor Yodaiken 
Finite State Machine Labs: The RTLinux Company.
 www.fsmlabs.com  www.rtlinux.com


  reply	other threads:[~2002-03-16  3:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  1:51 2.4.18 Preempt Freezeups Ian Duggan
2002-03-15  1:54 ` Robert Love
2002-03-15  8:36   ` Ian Duggan
2002-03-15 14:25     ` Robert Love
2002-03-15 16:11       ` Mikael Pettersson
2002-03-15 19:11         ` Robert Love
2002-03-16  0:40           ` yodaiken
2002-03-16  1:46             ` Mike Fedyk
2002-03-16  3:12               ` yodaiken [this message]
2002-03-17  0:33             ` Daniel Phillips
2002-03-17  1:13               ` yodaiken
2002-03-17  1:14                 ` Daniel Phillips
2002-03-17  1:54                   ` yodaiken
2002-03-17  2:08                     ` Daniel Phillips
2002-03-17 21:17                     ` Davide Libenzi
2002-03-15 14:30     ` Alan Cox
2002-03-15 21:36       ` Ian Duggan
2002-03-15  2:11 ` Alan Cox
2002-03-15  8:38   ` Ian Duggan
2002-03-15  8:51     ` David S. Miller
2002-03-15 14:28     ` Alan Cox
2002-03-16 23:51       ` Daniel Phillips
2002-03-17  3:31         ` Alan Cox
2002-03-17 12:59           ` Dave Jones
2002-03-15  8:43   ` Daniel Phillips

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=20020315201240.A7368@hq.fsmlabs.com \
    --to=yodaiken@fsmlabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=rml@tech9.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 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.