On Mon, Mar 30, 2015 at 04:20:10PM -0700, Dmitry Torokhov wrote: > From: "Luis R. Rodriguez" <[email protected]> > > Folks wishing to test enabling async probe for all built-in drivers > and/or for all modules can use > __DEBUG__kernel_force_builtin_async_probe or > __DEBUG__kernel_force_modules_async_probe kernel parameters. > > Activating either one will taint your kernel. > > Signed-off-by: Luis R. Rodriguez <[email protected]> > [Dmitry: split off from another patch, split into 2 parameters, moved > over to core_param_unsafe()] > Signed-off-by: Dmitry Torokhov <[email protected]>
I've dropped this from my tree as I don't want to add these options, only to have to remove them later on when it's found out that these were a bad idea. I don't want to create a user api that we have to keep around for forever, and this would be such a thing (specifying how the kernel probing works.) For debugging, can't you just patch up your kernel and test this out? What's the real use of this? Who do you want to enable these? And why? What will you do with the information? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
