On 2 January 2014 02:34, Xishi Qiu <qiuxishi@xxxxxxxxxx> wrote: > On 2013/12/31 18:12, Vegard Nossum wrote: >> On 31 December 2013 09:32, Xishi Qiu <qiuxishi@xxxxxxxxxx> wrote: >>> Add a new command-line kmemcheck value: kmemcheck=3 (disable the feature), >>> this is the same effect as CONFIG_KMEMCHECK disabled. >>> After doing this, we can enable/disable kmemcheck feature in one vmlinux. >> >> Could you please explain what exactly the difference is between the >> existing kmemcheck=0 parameter and the new kmemcheck=3? > > kmemcheck=0: enable kmemcheck feature, but don't check the memory. > and the OS use only one cpu.(setup_max_cpus = 1) > kmemcheck=3: disable kmemcheck feature. > this is the same effect as CONFIG_KMEMCHECK disabled. > OS will use cpus as many as possible. > I see. In that case, I think it's better to allow all the CPUs to keep running while kmemcheck is disabled with kmemcheck=0 boot parameter, and offline them when/if kmemcheck is reenabled via /proc/sys/kernel/kmemcheck. Vegard -- 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>