From: Xishi Qiu <qiuxishi@huawei.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Vegard Nossum <vegardno@ifi.uio.no>,
Pekka Enberg <penberg@kernel.org>, Mel Gorman <mgorman@suse.de>,
wangnan0@huawei.com, the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: add a new command-line kmemcheck value
Date: Thu, 2 Jan 2014 09:34:14 +0800 [thread overview]
Message-ID: <52C4C216.3070607@huawei.com> (raw)
In-Reply-To: <CAOMGZ=GOR_i9ixvHeHwfDN1wwwSQzFNFGa4qLZMhWWNzx0p8mw@mail.gmail.com>
On 2013/12/31 18:12, Vegard Nossum wrote:
> (Oops, resend to restore Cc.)
>
> Hi,
>
> On 31 December 2013 09:32, Xishi Qiu <qiuxishi@huawei.com> 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?
>
> Thanks,
>
>
> Vegard
>
Hi Vegard,
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.
Thanks,
Xishi Qiu
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-01-02 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 8:32 Xishi Qiu
2013-12-31 10:12 ` Vegard Nossum
2014-01-02 1:34 ` Xishi Qiu [this message]
2014-01-10 16:02 ` Vegard Nossum
2014-01-22 1:22 ` Xishi Qiu
2014-02-11 7:17 ` Xishi Qiu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52C4C216.3070607@huawei.com \
--to=qiuxishi@huawei.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=vegard.nossum@gmail.com \
--cc=vegardno@ifi.uio.no \
--cc=wangnan0@huawei.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox