On Mon, Oct 06, 2014 at 04:19:26PM -0400, Tejun Heo wrote: > Hello, Luis. > > The patchset generally looks good to me. Please feel free to add > > Reviewed-by: Tejun Heo <tj@xxxxxxxxxx> Will do. > A question below. > > On Fri, Oct 03, 2014 at 02:44:43PM -0700, Luis R. Rodriguez wrote: > > + bus.enable_kern_async=1 [KNL] > > + This tells the kernel userspace has been vetted for > > + asynchronous probe support and can listen to the device > > + driver prefer_async_probe flag for both built-in device > > + drivers and modules. > > Do we intend to keep this param permanently? Isn't this more of a > temp tool to be used during development? If so, maybe we should make > that clear with __DEVEL__ too? As its designed right now no, its not a temp tool, its there to require compatibility with old userspace. For modules we can require the module parameter but for built-in we need something else and this is what came to mind. It is also what would allow the prefer_async_probe flag too as otherwise we won't know if userspace is prepared. If we want to get rid of it, it would mean that we're letting go of the idea that some userspace might exist which depends on *not* doing async probe. As such I would not consider it a __DEVEL__ param and it'd be a judgement call to eventually *not require* it. I can see that happening but perhaps a large series of kernels down the road? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
