From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>, <ming.lei@redhat.com>
Subject: Re: [RFC PATCH] ACPI / processor: Get accurate possible CPU count
Date: Thu, 15 Mar 2018 11:00:39 +0800 [thread overview]
Message-ID: <95c1590a-1645-ce0e-dea3-d8927bc97704@cn.fujitsu.com> (raw)
In-Reply-To: <CAHp75VfGPgbD8gBdvchBn5U8gH93zoHB9ja3KucUuxVNq+_MLg@mail.gmail.com>
Hi Andy,
At 03/15/2018 01:24 AM, Andy Shevchenko wrote:
> On Wed, Mar 14, 2018 at 12:28 PM, Dou Liyang <douly.fnst@cn.fujitsu.com> wrote:
>
>> +static void __init acpi_update_possible_map(void)
>> +{
>> + unsigned int cpu, nr = 0;
>> +
>
>> + if (nr_cpu_ids <= nr_unique_ids)
>> + return;
>> +
>> + for_each_possible_cpu(cpu) {
>> + if (nr >= nr_unique_ids)
>> + set_cpu_possible(cpu, false);
>> + nr++;
>> + }
>
> IIUC this can be optimized to:
>
Yes, I agree, It's smarter and clearer. Will use it.
Thanks,
dou
> if (nr_unique_ids >= nr_cpu_ids)
> return;
>
> /* Don't yet figure out if it's superfluous */
> if (nr_unique_ids >= cpumask_last(cpu_possible_mask))
> return;
>
> for_each_cpu_wrap(cpu, cpu_possible_mask, nr_unique_ids)
> set_cpu_possible(cpu, false);
>
>> + nr_cpu_ids = nr_unique_ids;
>> + pr_info("Allowing %d possible CPUs\n", nr_cpu_ids);
>> +}
>
next prev parent reply other threads:[~2018-03-15 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 10:28 Dou Liyang
2018-03-14 17:24 ` Andy Shevchenko
2018-03-15 3:00 ` Dou Liyang [this message]
2018-03-16 11:17 ` [ACPI / processor] d619c81e24: WARNING:at_include/linux/cpumask.h:#cpumask_test_cpu kernel test robot
2018-03-16 11:17 ` kernel test robot
2018-03-19 0:41 ` 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=95c1590a-1645-ce0e-dea3-d8927bc97704@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=andy.shevchenko@gmail.com \
--cc=dedekind1@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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®