linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep.Holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: use num_possible_cpus() instead of NR_CPUS
Date: Tue, 28 Jan 2014 10:11:13 +0000	[thread overview]
Message-ID: <52E78241.4020502@arm.com> (raw)
In-Reply-To: <001d01cf1bc9$452569d0$cf703d70$%han@samsung.com>

On 28/01/14 01:35, Jingoo Han wrote:
> Use num_possible_cpus() instead of direct use of NR_CPUS. Also,
> it fixes the following checkpatch warning.
> 
>   WARNING: usage of NR_CPUS is often wrong - consider using cpu_possible(), num_possible_cpus(), for_each_possible_cpu(), etc
> 
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
>  arch/arm64/kernel/smp.c |   10 +++++-----
>  arch/arm64/mm/context.c |    2 +-
>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
> index 1b7617a..09ff7d4 100644
> --- a/arch/arm64/kernel/smp.c
> +++ b/arch/arm64/kernel/smp.c
> @@ -320,7 +320,7 @@ void __init smp_init_cpus(void)
>  		 * cpu_logical_map was initialized to INVALID_HWID to
>  		 * avoid matching valid MPIDR values.
>  		 */
> -		for (i = 1; (i < cpu) && (i < NR_CPUS); i++) {
> +		for (i = 1; (i < cpu) && (i < num_possible_cpus()); i++) {
>  			if (cpu_logical_map(i) == hwid) {
>  				pr_err("%s: duplicate cpu reg properties in the DT\n",
>  					dn->full_name);
> @@ -352,7 +352,7 @@ void __init smp_init_cpus(void)
>  			continue;
>  		}
>  
> -		if (cpu >= NR_CPUS)
> +		if (cpu >= num_possible_cpus())

Have you tested this patch ? IIUC this will not work as cpu_possible mask is
populated completely and correctly only at the end of this function.

>  			goto next;
>  
>  		if (cpu_read_ops(dn, cpu) != 0)
> @@ -368,9 +368,9 @@ next:
>  	}
>  
>  	/* sanity check */
> -	if (cpu > NR_CPUS)
> +	if (cpu > num_possible_cpus())
>  		pr_warning("no. of cores (%d) greater than configured maximum of %d - clipping\n",
> -			   cpu, NR_CPUS);
> +			   cpu, num_possible_cpus());
>  
>  	if (!bootcpu_valid) {
>  		pr_err("DT missing boot CPU MPIDR, not enabling secondaries\n");
> @@ -381,7 +381,7 @@ next:
>  	 * All the cpus that made it to the cpu_logical_map have been
>  	 * validated so set them as possible cpus.
>  	 */
> -	for (i = 0; i < NR_CPUS; i++)
> +	for (i = 0; i < num_possible_cpus(); i++)
>  		if (cpu_logical_map(i) != INVALID_HWID)
>  			set_cpu_possible(i, true);

This is what I am referring above, where is possible mask set before this.
If it's already populated correctly then we can remove this completely.

Regards,
Sudeep

  parent reply	other threads:[~2014-01-28 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  1:35 [PATCH 1/2] arm64: use num_possible_cpus() instead of NR_CPUS Jingoo Han
2014-01-28  1:36 ` [PATCH 2/2] arm64: kernel: use seq_puts() instead of seq_printf() Jingoo Han
2014-01-28 15:51   ` Catalin Marinas
2014-01-29  4:54     ` Jingoo Han
2014-01-29  5:00       ` Joe Perches
2014-01-28 10:11 ` Sudeep Holla [this message]
2014-01-29  5:31   ` [PATCH 1/2] arm64: use num_possible_cpus() instead of NR_CPUS Jingoo Han

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=52E78241.4020502@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).