public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric <eric@cisu.net>
To: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: Correct CPUs printout on boot.
Date: Fri, 23 Jan 2004 17:03:54 -0600	[thread overview]
Message-ID: <200401231703.54127.eric@cisu.net> (raw)
In-Reply-To: <E1Ajuub-0000y1-00@hardwired>

On Friday 23 January 2004 12:35 am, davej@redhat.com wrote:
> This currently prints out the maximum number of CPUs the
> kernel is configured to support, instead of the actual
> number that the kernel brought up. Which results in odd
> displays that look like you have more CPUs than you do.

Why do you have to declare a new variable? Can't you just do this? i is 
already counting how many cpu's we've brought up and its of the same type j.

-	printk("CPUS done %u\n", max_cpus);
+	printk("CPUS done %u\n", i);


>     Dave
>
> diff -urpN --exclude-from=/home/davej/.exclude bk-linus/init/main.c
> linux-2.5/init/main.c --- linux-2.5/init/main.c~	Fri Jan 23 06:24:12 2004
> +++ linux-2.5/init/main.c	Fri Jan 23 06:24:44 2004
> @@ -339,7 +339,7 @@
>  /* Called by boot processor to activate the rest. */
>  static void __init smp_init(void)
>  {
> -	unsigned int i;
> +	unsigned int i, j=0;
>
>  	/* FIXME: This should be done in userspace --RR */
>  	for (i = 0; i < NR_CPUS; i++) {
> @@ -348,11 +348,12 @@
>  		if (cpu_possible(i) && !cpu_online(i)) {
>  			printk("Bringing up %i\n", i);
>  			cpu_up(i);
> +			j++;
>  		}
>  	}
>
>  	/* Any cleanup work */
> -	printk("CPUS done %u\n", max_cpus);
> +	printk("CPUS done %u\n", j);
>  	smp_cpus_done(max_cpus);
>  #if 0
>  	/* Get other processors into their bootup holding patterns. */

 
-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------

  reply	other threads:[~2004-01-23 23:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  6:35 Correct CPUs printout on boot davej
2004-01-23 23:03 ` Eric [this message]
2004-01-24  2:25   ` Nick Piggin

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=200401231703.54127.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.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