On Wed, 25 Apr 2018, James Bottomley wrote: > > BTW. even developers who compile their own kernel should have this > > enabled by a CONFIG option - because if the developer sees the option > > when browsing through menuconfig, he may enable it. If he doesn't see > > the option, he won't even know that such an option exists. > > I may be an atypical developer but I'd rather have a root canal than > browse through menuconfig options. The way to get people to learn > about new debugging options is to blog about it (or write an lwn.net > article) which google will find the next time I ask it how I debug XXX. > Google (probably as a service to humanity) rarely turns up Kconfig > options in response to a query. >From my point of view, this feature should be as little disruptive to the developer as possible. It should work automatically behind the scenes without the developer or the tester even knowing that it is working. From this point of view, binding it to CONFIG_DEBUG_SG (or any other commonly used debugging option) would be ideal, because driver developers already enable CONFIG_DEBUG_SG, so they'll get this kvmalloc test for free. >From your point of view, you should introduce a sysfs file and a kernel parameter that no one knows about - and then start blogging about it - to let people know. Why would you bother people with this knowledge? They'll forget about it anyway and won't turn it on. Mikulas
