Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 15 Mar 2003 15:48:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 15 Mar 2003 15:48:30 -0500 Received: from modemcable092.130-200-24.mtl.mc.videotron.ca ([24.200.130.92]:22312 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id ; Sat, 15 Mar 2003 15:48:29 -0500 Date: Sat, 15 Mar 2003 15:55:43 -0500 (EST) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: bert hubert cc: dan carpenter , Linux Kernel , "" , Pavel Machek Subject: Re: Any hope for ide-scsi (error handling)? In-Reply-To: Message-ID: References: <200303151926.h2FJQLnB103490@pimout1-ext.prodigy.net> <200303152012.h2FKCulK283698@pimout2-ext.prodigy.net> <20030315202509.GA4374@outpost.ds9a.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 887 Lines: 25 On Sat, 15 Mar 2003, Zwane Mwaikambo wrote: > On Sat, 15 Mar 2003, bert hubert wrote: > > > A construct like this was suggested for use in swsusp too to make sure that > > only *one* request is outstanding for a controler. This was also mentioned > > to be the unclean way and that there are taskfile interfaces which are > > cleaner. [snip] > Ok so at event [1] we have a ->handler set on cpu0 so we pass that check. > Then cpu1 acquires ide_lock and NULLs it out. cpu0 blocks on the lock in > ide_set_handler and when cpu1 releases it it re-assigns ->handler. What > happens then? Skip that, i forgot swsusp doesn't do SMP. Zwane - 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/