Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750849AbaABBgW (ORCPT ); Wed, 1 Jan 2014 20:36:22 -0500 Received: from szxga02-in.huawei.com ([119.145.14.65]:1832 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750704AbaABBgV (ORCPT ); Wed, 1 Jan 2014 20:36:21 -0500 Message-ID: <52C4C216.3070607@huawei.com> Date: Thu, 2 Jan 2014 09:34:14 +0800 From: Xishi Qiu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Vegard Nossum CC: Ingo Molnar , "H. Peter Anvin" , "Vegard Nossum" , Pekka Enberg , Mel Gorman , , the arch/x86 maintainers , LKML , Linux MM Subject: Re: [PATCH] mm: add a new command-line kmemcheck value References: <52C2811C.4090907@huawei.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.135.74.196] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1061 Lines: 39 On 2013/12/31 18:12, Vegard Nossum wrote: > (Oops, resend to restore Cc.) > > Hi, > > On 31 December 2013 09:32, Xishi Qiu 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/