Re: [PATCH] mm: add a new command-line kmemcheck value
From: Xishi Qiu
Date: Tue Jan 21 2014 - 20:25:19 EST
On 2014/1/11 0:02, Vegard Nossum wrote:
> 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
In some scenes, user want to check memory dynamicly, this "dynamically"
means we can turn on/off the feature at boottime, not runtime. Without
this patch, if user want to use this feature, he should change config
and build the kernel, then reboot. This is impossilbe if user has no
kernel code or he don't know how to build the kernel.
boottime: kmemcheck=0/1/2/3 (command-line)
runtime: kmemcheck=0/1/2 (/proc/sys/kernel/kmemcheck)
The main different between kmemcheck=0 and 3 is the used memory. Kmemcheck
will use about twice as much memory as normal.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/