From: Peter Zijlstra <peterz@infradead.org>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-doc@vger.kernel.org,
tglx@linutronix.de, 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
Date: Tue, 20 Mar 2018 13:37:12 +0100 [thread overview]
Message-ID: <20180320123712.GR4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180320110432.28127-2-douly.fnst@cn.fujitsu.com>
On Tue, Mar 20, 2018 at 07:04:28PM +0800, Dou Liyang wrote:
> + 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.
That description, esp. the last sentence, doesn't make any kind of sense
to me. What?
next prev parent reply other threads:[~2018-03-20 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:04 [PATCH 0/5] x86/cpu_hotplug: one bug fix and four cleanup Dou Liyang
2018-03-20 11:04 ` [PATCH 1/5] x86/smpboot: Add the missing description of possible_cpus Dou Liyang
2018-03-20 12:37 ` Peter Zijlstra [this message]
2018-03-21 5:33 ` Dou Liyang
2018-03-21 9:08 ` Peter Zijlstra
2018-03-21 9:34 ` Dou Liyang
2018-03-21 9:41 ` Dou Liyang
2018-03-21 9:41 ` Thomas Gleixner
2018-03-20 11:04 ` [PATCH 2/5] x86/cpu_hotplug: Update the link of cpu_hotplug.rst Dou Liyang
2018-03-20 11:04 ` [PATCH 3/5] x86/smpboot: Make the check code more clear in prefill_possible_map() Dou Liyang
2018-03-20 12:39 ` Peter Zijlstra
2018-03-21 5:38 ` Dou Liyang
2018-03-20 11:04 ` [PATCH 4/5] acpi/processor: Fix the return value of acpi_processor_ids_walk() Dou Liyang
2018-05-19 15:06 ` Thomas Gleixner
2018-05-22 1:47 ` Dou Liyang
2018-05-23 1:34 ` Dou Liyang
2018-05-23 8:08 ` Rafael J. Wysocki
2018-03-20 11:04 ` [PATCH 5/5] acpi/processor: Make the acpi_duplicate_processor_id() static Dou Liyang
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=20180320123712.GR4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=corbet@lwn.net \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--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