All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Linux cannot run with 0 cores
Date: Fri, 18 Jun 2010 11:02:22 -0700	[thread overview]
Message-ID: <20100618180222.GH2365@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100618003306.GA3463@kryten>

On Fri, Jun 18, 2010 at 10:33:06AM +1000, Anton Blanchard wrote:
> 
> If we configure with CONFIG_SMP=n or set NR_CPUS less than the number of
> SMT threads we will set the max cores property to 0 in the
> ibm,client-architecture-support structure. On new versions of firmware that
> understand this property it obliges and terminates our partition.
> 
> Use DIV_ROUND_UP so we handle not only the CONFIG_SMP=n case but also the
> case where NR_CPUS isn't a multiple of the number of SMT threads.

Thank you, Anton!!!

Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

(Will test as soon as the system that hit this becomes available.)

> Signed-off-by: Anton Blanchard <anton@samba.org>
> ---
> 
> Index: linux-2.6/arch/powerpc/kernel/prom_init.c
> ===================================================================
> --- linux-2.6.orig/arch/powerpc/kernel/prom_init.c	2010-06-17 09:08:20.000000000 +1000
> +++ linux-2.6/arch/powerpc/kernel/prom_init.c	2010-06-17 09:10:02.000000000 +1000
> @@ -872,7 +872,7 @@ static void __init prom_send_capabilitie
>  				    "ibm_architecture_vec structure inconsistent: 0x%x !\n",
>  				    *cores);
>  		} else {
> -			*cores = NR_CPUS / prom_count_smt_threads();
> +			*cores = DIV_ROUND_UP(NR_CPUS, prom_count_smt_threads());
>  			prom_printf("Max number of cores passed to firmware: 0x%x\n",
>  				    (unsigned long)*cores);
>  		}

      reply	other threads:[~2010-06-18 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18  0:33 [PATCH] powerpc: Linux cannot run with 0 cores Anton Blanchard
2010-06-18 18:02 ` Paul E. McKenney [this message]

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=20100618180222.GH2365@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.