On Mon 14-08-17 10:01:52, Pasha Tatashin wrote: > >>However, now thinking about it, I will change it to CONFIG_MEMBLOCK_DEBUG, > >>and let users decide what other debugging configs need to be enabled, as > >>this is also OK. > > > >Actually the more I think about it the more I am convinced that a kernel > >boot parameter would be better because it doesn't need the kernel to be > >recompiled and it is a single branch in not so hot path. > > The main reason I do not like kernel parameter is that automated test suits > for every platform would need to be updated to include this new parameter in > order to test it. How does this differ from the enabling a config option and building a separate kernel? My primary point of the kernel option was to have something available to debug without recompiling the kernel which is more tedious than simply adding one option to the kernel command line. -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
