From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mtagate6.uk.ibm.com (mtagate6.uk.ibm.com [195.212.29.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mtagate6.uk.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTP id C0A9BDDE3B for ; Thu, 19 Jul 2007 22:00:43 +1000 (EST) Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate6.uk.ibm.com (8.13.8/8.13.8) with ESMTP id l6JC0c3I210542 for ; Thu, 19 Jul 2007 12:00:38 GMT Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1407.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v8.4) with ESMTP id l6JC0cwT2695296 for ; Thu, 19 Jul 2007 13:00:38 +0100 Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l6JC0Lwn029017 for ; Thu, 19 Jul 2007 13:00:21 +0100 Date: Thu, 19 Jul 2007 14:00:38 +0200 From: Cornelia Huck To: Geert Uytterhoeven Subject: Re: [patch 1/3] ps3: Disk Storage Driver Message-ID: <20070719140038.606abd44@gondolin.boeblingen.de.ibm.com> In-Reply-To: References: <20070716161539.075822000@pademelon.sonytel.be> <20070716162206.392129000@pademelon.sonytel.be> <20070718163637.3f0e0164.akpm@linux-foundation.org> <20070719112602.5e3cb21a@gondolin.boeblingen.de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: Jens Axboe , "James E.J. Bottomley" , Jens Axboe , linux-scsi@vger.kernel.org, Development , Linux/PPC Development , Paul Mackerras , Linux, Andrew Morton List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 19 Jul 2007 11:36:31 +0200 (CEST), Geert Uytterhoeven wrote: > We have a probe thread that checks for new storage devices and adds them to the > bus with ps3_system_bus_device_register(), which calls device_register(). > > I guess the actual bus probe() routine gets called through the notifier call > chain? That's where I got lost... No, ->probe() is called from device_register() directly. If you just have one probe thread, you should have enough serialization. (Unless you're doing something interesting from the bus_notifier, which is called via the notifier chain before ->probe()...)