All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [patch] logical CPU numbering
Date: Thu, 03 Apr 2003 18:31:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705399@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705277@msgid-missing>

On Thu, Mar 20, 2003 at 02:03:57PM -0500, Martin Hicks wrote:
> 
> Hello,
> 
> If a CPU fails to start during smp_boot_cpus(), then the logical CPU
> numbering gets will have a "hole".  Using the number of booted CPU's
> instead of the loop index will correct this.
> 
> This patch is against 2.4.21-pre5.

This patch should be applied.  I finally got around to doing some more
testing with it.  If a CPU fails to start, currently we get messages
like the following for subsequent CPU's:


CPU 17: nasid 18, slice 0, cnode 9
CPU 17: base freq 0.000MHz, ITC ratio\x10/2, ITC freq\x1000.000MHz
Calibrating delay loop... 1494.72 BogoMIPS
phys CPU#17 (0x12) not responding - cannot use it.               <<-BOGUS


The patch below fixes this problem.  This is the same patch as before,
reposted just to make things easier.  It is against
2.4.21-pre5-ia64-0303012.

Thanks,
mh

-- 
Wild Open Source Inc.                  mort@wildopensource.com


--- linux-2.4.21-pre5-ia64-030312.pristine/arch/ia64/kernel/smpboot.c	Sun Mar 16 10:18:53 2003
+++ linux-2.4.21-pre5-ia64-030312/arch/ia64/kernel/smpboot.c	Thu Mar 20 10:47:07 2003
@@ -522,7 +522,7 @@
 			/*
 			 * Make sure we unmap all failed CPUs
 			 */
-			if (ia64_cpu_to_sapicid[cpu] = -1)
+			if (ia64_cpu_to_sapicid[cpucount] = -1)
 				printk("phys CPU#%d not responding - cannot use it.\n", cpu);
 		}
 


  parent reply	other threads:[~2003-04-03 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 19:03 [Linux-ia64] [patch] logical CPU numbering Martin Hicks
2003-03-20 20:07 ` Wichmann, Mats D
2003-03-25 18:03 ` Martin Hicks
2003-04-03 18:31 ` Martin Hicks [this message]
2003-04-17 19:13 ` Bjorn Helgaas
2003-04-17 20:25 ` Martin Hicks

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=marc-linux-ia64-105590723705399@msgid-missing \
    --to=mort@wildopensource.com \
    --cc=linux-ia64@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 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.