Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 16 Mar 2002 20:21:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 16 Mar 2002 20:20:53 -0500 Received: from dsl-213-023-039-132.arcor-ip.net ([213.23.39.132]:26317 "EHLO starship") by vger.kernel.org with ESMTP id ; Sat, 16 Mar 2002 20:20:47 -0500 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: yodaiken@fsmlabs.com, Daniel Phillips Subject: Re: 2.4.18 Preempt Freezeups Date: Sun, 17 Mar 2002 02:14:14 +0100 X-Mailer: KMail [version 1.3.2] Cc: yodaiken@fsmlabs.com, Robert Love , Mikael Pettersson , linux kernel In-Reply-To: <3C9153A7.292C320@ianduggan.net> <20020316181338.A26242@hq.fsmlabs.com> In-Reply-To: <20020316181338.A26242@hq.fsmlabs.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On March 17, 2002 02:13 am, yodaiken@fsmlabs.com wrote: > On Sun, Mar 17, 2002 at 01:33:04AM +0100, Daniel Phillips wrote: > > On March 16, 2002 01:40 am, yodaiken@fsmlabs.com wrote: > > > > > > Without preempt: > > > x = movefrom processor register; > // if preemption is on, we can be preempted and restart > // on another processor so x will be wrong > > > do_something with x > > > > > > is safe in SMP > > > With [preempt] it requires a lock. > > > > It must be a trick question. Why would it? > > See comment. Which processor register were you thinking of? Surely not anything in the general register set, and otherwise, it's just another example of per-cpu data. It needs to be protected, and the protection is lightweight. -- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/