Re: [PATCH 2.5.52] Use __set_current_state() instead of current-> state = (take 1)

From: Oliver Xymoron (oxymoron@waste.org)
Date: Fri Dec 20 2002 - 14:36:20 EST

Next message: Greg KH: "Re: Please use the 'usbfs' filetype instead"
Previous message: Ruslan U. Zakirov: "fbset in startup script and atyfb problems."
In reply to: Alan Cox: "RE: [PATCH 2.5.52] Use __set_current_state() instead of current-> state = (take 1)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, Dec 20, 2002 at 03:08:28AM +0000, Alan Cox wrote:
> In addition you have to treat store ordering/locking carefully due to
> the pentium pro store fencing errata. (Thats why our < PII kernel
> generates lock movb to unlock when in theory the lock isnt needed).

Except the SMP causality test app I wrote got success reports from every
PPro stepping level.

-- 
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.." 
-
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/

Next message: Greg KH: "Re: Please use the 'usbfs' filetype instead"
Previous message: Ruslan U. Zakirov: "fbset in startup script and atyfb problems."
In reply to: Alan Cox: "RE: [PATCH 2.5.52] Use __set_current_state() instead of current-> state = (take 1)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Dec 23 2002 - 22:00:27 EST