From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
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 3/5] x86/smpboot: Make the check code more clear in prefill_possible_map()
Date: Wed, 21 Mar 2018 13:38:44 +0800 [thread overview]
Message-ID: <e9ef4100-0b87-b61a-5ad4-5f78b2d61783@cn.fujitsu.com> (raw)
In-Reply-To: <20180320123918.GS4043@hirez.programming.kicks-ass.net>
Hi Peter,
At 03/20/2018 08:39 PM, Peter Zijlstra wrote:
> On Tue, Mar 20, 2018 at 07:04:30PM +0800, Dou Liyang wrote:
>> case 1: no | no | no | --> min (setup_possible_cpus, nr_cpu_ids, setup_max_cpus)
>> case 2: no | no | yes| --> min (setup_possible_cpus, nr_cpu_ids)
>> case 3: no | yes | no | --> 1
>> case 4: no | yes | yes| --> 1
>> case 5: yes | no | no | --> min (num_processors, nr_cpu_ids, setup_max_cpus)
>> case 6: yes | no | yes| --> min (num_processors + disabled_cpus, nr_cpu_ids)
>> case 7: yes | yes | no | --> 1
>> case 8: yes | yes | yes| --> 1
>
> The case number is off by one ;-)
>
I got it! ;-)
Thanks
dou
>
>
next prev parent reply other threads:[~2018-03-21 5:38 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
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 [this message]
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=e9ef4100-0b87-b61a-5ad4-5f78b2d61783@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=corbet@lwn.net \
--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=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®