From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752089AbaHaWvp (ORCPT ); Sun, 31 Aug 2014 18:51:45 -0400 Received: from mail-pa0-f53.google.com ([209.85.220.53]:47382 "EHLO mail-pa0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751667AbaHaWvo (ORCPT ); Sun, 31 Aug 2014 18:51:44 -0400 Date: Sun, 31 Aug 2014 15:51:40 -0700 From: Dmitry Torokhov To: Tejun Heo Cc: Greg KH , Arjan van de Ven , "Luis R. Rodriguez" , falcon@meizu.com, tiwai@suse.de, linux-kernel@vger.kernel.org, oleg@redhat.com, akpm@linux-foundation.org, penguin-kernel@i-love.sakura.ne.jp, joseph.salisbury@canonical.com, bpoirier@suse.de, "Luis R. Rodriguez" Subject: Re: [RFC v1 0/3] driver-core: add asynch module loading support Message-ID: <20140831225140.GA20569@core.coreip.homeip.net> References: <1409475800-17573-1-git-send-email-mcgrof@do-not-panic.com> <540334B2.7000009@linux.intel.com> <20140831175040.GA17827@core.coreip.homeip.net> <5403767E.1020107@linux.intel.com> <20140831193140.GA12678@kroah.com> <20140831201407.GB19881@core.coreip.homeip.net> <20140831204035.GA4793@kroah.com> <20140831215313.GA28690@mtj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140831215313.GA28690@mtj.dyndns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 31, 2014 at 05:53:13PM -0400, Tejun Heo wrote: > Hello, Greg. > > On Sun, Aug 31, 2014 at 01:40:35PM -0700, Greg KH wrote: > > > Right, all (well almost all) I wanted is for individual drivers to declare > > > their probe() functions asynchronous and driver core scheduling async attach > > > and properly handle failures from it. > > > > Yes, that's what I want as well. > > > > Luis, care to redo the patches in this way? It should be a lot simpler > > (no messing around with init levels and linker fun...) > > I don't think binding that switch to the driver is gonna work. This > is mainly about the behavior expected by the entity which initiated > module loading not about specific drivers. Why would you say that? In my particular userspace we do not have modules. > I'm fairly certain that > there are userland scripts which depend on synchronous device probing > on module loading, especially for storage devices, so we can't simply > mark, say, libata as needing async probing and do it always > asynchronously. Right. But for many devices (input ones for example, USB as well, etc) that are essentially hot-pluggable userspace has been long ready to handle async order. Thanks. -- Dmitry