From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757254AbcAJPNg (ORCPT ); Sun, 10 Jan 2016 10:13:36 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:36260 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757090AbcAJPNe (ORCPT ); Sun, 10 Jan 2016 10:13:34 -0500 From: Ameen X-Google-Original-From: Ameen To: mingo@kernel.org, peterz@infradead.org, mhocko@suse.com, vbabka@suse.cz Cc: linux-kernel@vger.kernel.org, Ameen Subject: [PATCH 2/2] Use num_possible_cpus() instead of direct use of NR_CPUS. Date: Sun, 10 Jan 2016 17:13:25 +0200 Message-Id: <1452438805-3205-1-git-send-email-AmeenAli023@gmail.com> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org WARNING: usage of NR_CPUS is often wrong - consider using cpu_possible(), num_possible_cpus().. Signed-off-by : Ameen Ali --- kernel/smp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/smp.c b/kernel/smp.c index d903c02..94033ac 100644 --- a/kernel/smp.c +++ b/kernel/smp.c @@ -549,13 +549,13 @@ static int __init maxcpus(char *str) early_param("maxcpus", maxcpus); /* Setup number of possible processor ids */ -int nr_cpu_ids __read_mostly = NR_CPUS; +int nr_cpu_ids __read_mostly = num_possible_cpus(); EXPORT_SYMBOL(nr_cpu_ids); /* An arch may set nr_cpu_ids earlier if needed, so this would be redundant */ void __init setup_nr_cpu_ids(void) { - nr_cpu_ids = find_last_bit(cpumask_bits(cpu_possible_mask),NR_CPUS) + 1; + nr_cpu_ids = find_last_bit(cpumask_bits(cpu_possible_mask),num_possible_cpus()) + 1; } void __weak smp_announce(void) -- 2.5.0