Subject: Re: 2.4.18 Preempt Freezeups
To: ian@ianduggan.net (Ian Duggan)
Date: Fri, 15 Mar 2002 14:28:36 +0000 (GMT)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), rml@tech9.net (Robert Love),
        linux-kernel@vger.kernel.org (linux kernel)
In-Reply-To: <3C91B30D.A887A033@ianduggan.net> from "Ian Duggan" at Mar 15, 2002 12:38:37 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E16lshA-0003lX-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org

> What is required for preempt beyond "SMP safe" code? I thought the whole
> idea was to make the preemptions transparent to other code by utilizing
> the SMP critical regions?

SMP safe code
Actual source code when recompiling modules
Reviewing things like driver code use of disable_irq by hand
Reviewing driver code for situations where it requires a small timing delay
	and a large one is unacceptable
Checking anywhere you use the cpu id that you don't do somthing where it
	might change under you (eg per cpu variables)
-
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/