Received: by 10.213.65.68 with SMTP id h4csp303494imn; Tue, 20 Mar 2018 04:06:41 -0700 (PDT) X-Google-Smtp-Source: AG47ELuyNFsCNE0NnYd7CQERlBK9cVYlscSh2c1hOfwqCTuY65bZOZaf/DHBEpxlOS0G6DFJgIl7 X-Received: by 10.99.106.202 with SMTP id f193mr12036638pgc.334.1521544001119; Tue, 20 Mar 2018 04:06:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521544001; cv=none; d=google.com; s=arc-20160816; b=Raj6VKLmz/4jiFKrzPj4ZrwsoukHOnFxTrJ0g1ARf9dCmqUX7n+q7ST9GQJsNe6Umz 4/AajgchSP5+khicqnQXB8XzvIcIDCWBaI6aV59Qc57l0DV6wFFD6dhAkLWWEnpUMbWY Q9lDrzdjo8uRRej7hUFel8aSfDN8i/bkxeMV+NhQRS8iRj5/pQ4Q/CwmC7tbC5m6ISfe F8M7dNS5fJuBaohOzslZowiVxL36P1bnZFxiGsI4vpAqN375r8cb/3Uay9LsrjKXy0VM AwNifyc5lfVLlBFhscpS78Z1pgQdMt83lwjmW+vqBsDe69Zhk9Af/tgtocU/y5tkX/OX SMUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:arc-authentication-results; bh=Ayt/WzL64FKeaDBYP2CoJPR9e8+2R3sObifS2X/kMMs=; b=nQOqrxJYBpz8enio17W0x1xxKIIhryWkKqfGDPsLjxTlKL07GYf/AG78RQDSnmeXI1 jlrz2fSc/5Hq5hdioIVe+l90SJJMnnKEzNn7L8eE2OLzyJQJIJUtDgdE749KBUmC2ZNY F2hxwFLkhtm+mzp5R8gpWRABIf86Blq9MHVdJWYO2lrOtofgeU1bhlo5Y20cU+TpLUDj cWLHlX9tv0VDd1qznfqbAQAShx+BhKpclVIpxTFbZpkxsKFW1cbzhI5GMTbk9ly6Fo5o 29+O8wh5j+O6+1fbgrFXiaSw3X5PQOYAiIFskejCImLuoWWh8iiNe1PbyQM4Ngf97zRu p7mw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a59-v6si1417758plc.123.2018.03.20.04.06.26; Tue, 20 Mar 2018 04:06:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752866AbeCTLFX (ORCPT + 99 others); Tue, 20 Mar 2018 07:05:23 -0400 Received: from mail.cn.fujitsu.com ([183.91.158.132]:7319 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752839AbeCTLFS (ORCPT ); Tue, 20 Mar 2018 07:05:18 -0400 X-IronPort-AV: E=Sophos;i="5.43,368,1503331200"; d="scan'208";a="38002749" Received: from bogon (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 20 Mar 2018 19:05:12 +0800 Received: from G08CNEXCHPEKD02.g08.fujitsu.local (unknown [10.167.33.83]) by cn.fujitsu.com (Postfix) with ESMTP id 5261648AE76B; Tue, 20 Mar 2018 19:05:10 +0800 (CST) Received: from localhost.localdomain (10.167.226.106) by G08CNEXCHPEKD02.g08.fujitsu.local (10.167.33.89) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 20 Mar 2018 19:05:09 +0800 From: Dou Liyang To: , , , CC: , , , , , , , Dou Liyang Subject: [PATCH 1/5] x86/smpboot: Add the missing description of possible_cpus Date: Tue, 20 Mar 2018 19:04:28 +0800 Message-ID: <20180320110432.28127-2-douly.fnst@cn.fujitsu.com> X-Mailer: git-send-email 2.14.3 In-Reply-To: <20180320110432.28127-1-douly.fnst@cn.fujitsu.com> References: <20180320110432.28127-1-douly.fnst@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.167.226.106] X-yoursite-MailScanner-ID: 5261648AE76B.AF586 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: douly.fnst@cn.fujitsu.com X-Spam-Status: No Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kernel uses the possible_cpus in command line to reset the possible_cpus bits in cpu_possible_map. It doesn't be recorded in the kernel-parameters.txt Add its description in this document, also replace the wrong option additional_cpus with possible_cpus in cpu-gotplug-spec. Signed-off-by: Dou Liyang --- Documentation/admin-guide/kernel-parameters.txt | 5 +++++ Documentation/x86/x86_64/cpu-hotplug-spec | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index 1d1d53f85ddd..34f8a5f04e63 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -2832,6 +2832,11 @@ variables need be pre-allocated for later physical cpu hot plugging. + possible_cpus= [s390,x86_64] Use this to set hotpluggable cpus. + This option sets possible_cpus bits in cpu_possible_map. + Thus keeping the numbers of bits set constant even if + the machine gets rebooted. + nr_uarts= [SERIAL] maximum number of UARTs to be registered. numa_balancing= [KNL,X86] Enable or disable automatic NUMA balancing. diff --git a/Documentation/x86/x86_64/cpu-hotplug-spec b/Documentation/x86/x86_64/cpu-hotplug-spec index 3c23e0587db3..d218bc0bdaaa 100644 --- a/Documentation/x86/x86_64/cpu-hotplug-spec +++ b/Documentation/x86/x86_64/cpu-hotplug-spec @@ -16,6 +16,6 @@ it should have its LAPIC Enabled bit set to 0. Linux will use the number of disabled LAPICs to compute the maximum number of future CPUs. In the worst case the user can overwrite this choice using a command line -option (additional_cpus=...), but it is recommended to supply the correct +option (possible_cpus=...), but it is recommended to supply the correct number (or a reasonable approximation of it, with erring towards more not less) in the MADT to avoid manual configuration. -- 2.14.3