Received: by 10.213.65.68 with SMTP id h4csp1102887imn; Wed, 21 Mar 2018 02:42:53 -0700 (PDT) X-Google-Smtp-Source: AG47ELvJ6AdVBxd3U0DaxEo8+Y3FxdPt3dAZaB9AMWMMOmt/3EeCnU03qHmitQP+xdBT4iMpBEe1 X-Received: by 10.98.72.10 with SMTP id v10mr16366193pfa.148.1521625373110; Wed, 21 Mar 2018 02:42:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521625373; cv=none; d=google.com; s=arc-20160816; b=wfrz3fvmrnjaykppWjtF7PAQVVRaaEVb9VQxhLKimzHTLpU/pE2Te0VNlekCWJjfFC TgLyV5sAFdhIr4PvGAK14fc6vROkjnEFp8mB6zPAbfjF87N6LqowjW62QBXVHdqWmooI 94Jl1QaQJBqWXOGTgjmq6/nPPiqlSkLJcQ5k6bqk8Mi8vlrDUy9Gm5rJVQ9SKmTykoiT 332oB/eXam4wQENalpKggpRL4Tyf1fju+u4mz4nNNzccJ1gSjbBVca6OT+iPga9NRIBg ZD+aVlsoDejkHfDp9xJzsI0RJ5/k/NsSKRT8QDVMixSBXqRqmrRfEmv+3/3VSaNIBdKI +yKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=4XAhz82E57Pv95YEqfdpl0I+bhYcYIA39bephRIuYWU=; b=gMof7yugCW4NUBlmXCTjmcTthCmAp6cvnC68znA+fGJ9TbEqSc3f47uDDWXdrZMRy8 I3bjuc2miJqa150IwcYiVtO+gKGQUNBTkdnlpAFatXc5U7pSyyyYRF23HlD2g+QaMSu/ LuYAbtInpfIa+/WBvjbZhcF7QrVYJEnkAyKw8IbGY+ke332soS41IweKyr3Gky1afJtY xs+w/7XD4FMCoV+8TfBgC9zO76gzvvdkzKhuPxvw3Zq4pn3HkzW/oXdls8AAGmiqUWA+ OOEEMWbt8ky1xgiatBgcJdv1SAEblzmf+jZM/PuAsj0X0ddqSSbYmpBcuKz+kU1p7RDa zppA== 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 s24-v6si3240940plp.620.2018.03.21.02.42.39; Wed, 21 Mar 2018 02:42:53 -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 S1751464AbeCUJli (ORCPT + 99 others); Wed, 21 Mar 2018 05:41:38 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:36569 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751405AbeCUJlg (ORCPT ); Wed, 21 Mar 2018 05:41:36 -0400 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1eyaFI-0003T3-7L; Wed, 21 Mar 2018 10:41:24 +0100 Date: Wed, 21 Mar 2018 10:41:21 +0100 (CET) From: Thomas Gleixner To: Peter Zijlstra cc: Dou Liyang , linux-kernel@vger.kernel.org, x86@kernel.org, linux-acpi@vger.kernel.org, linux-doc@vger.kernel.org, mingo@redhat.com, corbet@lwn.net, rjw@rjwysocki.net, lenb@kernel.org, hpa@zytor.com Subject: Re: [PATCH 1/5] x86/smpboot: Add the missing description of possible_cpus In-Reply-To: <20180321090826.GW4043@hirez.programming.kicks-ass.net> Message-ID: References: <20180320110432.28127-1-douly.fnst@cn.fujitsu.com> <20180320110432.28127-2-douly.fnst@cn.fujitsu.com> <20180320123712.GR4043@hirez.programming.kicks-ass.net> <20180321090826.GW4043@hirez.programming.kicks-ass.net> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Mar 2018, Peter Zijlstra wrote: > On Wed, Mar 21, 2018 at 01:33:24PM +0800, Dou Liyang wrote: > > How about: > > > > possible_cpus= [s390,x86_64] Set the number of possible CPUs which > > are determined by the ACPI tables MADT or mptables by > > default. possible_cpus=n : n >= 1 enforces the possible > > number to be 'n'. > > While nr_cpus is also be set: nr_cpus=m, choice the > > minimum one for the number of possible CPUs. > > So what is the exact difference between possible_cpus and nr_cpus ? I > konw maxcpus= limits the number of CPUs we bring up, and possible_cpus > limits the possible_map, but I'm not entirely sure what nr_cpus does > here. nr_cpus limits the number of CPUs the kernel will handle. Think of it as a boot time override of NR_CPUs. Way too many commandline switches though. Thanks, tglx