public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - Pass OS logical cpu number to the SN prom (bios)
Date: Thu, 27 Apr 2006 23:54:36 +0000	[thread overview]
Message-ID: <15771.1146182076@ocs3.ocs.com.au> (raw)
In-Reply-To: <20060427220857.GA14901@sgi.com>

Jack Steiner (on Thu, 27 Apr 2006 17:08:58 -0500) wrote:
>Pass the OS logical cpu number to the PROM. This allows PROM to 
>log the OS logical cpu number in error records viewed thru POD.
>This signifinantly simplifies diagnosis of hardware errors on 
>large systems.
>
>	Signed-off-by: Jack Steiner <steiner@sgi.com>
>
>
>
>Index: linux/arch/ia64/sn/kernel/setup.c
>=================================>--- linux.orig/arch/ia64/sn/kernel/setup.c	2006-04-22 08:50:14.567000831 -0500
>+++ linux/arch/ia64/sn/kernel/setup.c	2006-04-27 17:02:24.646672915 -0500
>@@ -597,6 +597,12 @@ void __init sn_cpu_init(void)
> 	sn_hub_info->as_shift = sn_hub_info->nasid_shift - 2;
> 
> 	/*
>+	 * Don't check status. The SAL call is not supported on all PROMs
>+	 * but a failure is harmless.
>+	 */
>+	(void) ia64_sn_set_cpu_number(smp_processor_id());
>+
>+	/*
> 	 * The boot cpu makes this call again after platform initialization is
> 	 * complete.
> 	 */

Nit pick.  sn_cpu_init() defines a cpuid variable which is set to
smp_processor_id(), but smp_processor_id() is used once (twice with
this patch) before cpuid is defined and used.  Move the definition of
cpuid to the top of the function and use it throughout.


  reply	other threads:[~2006-04-27 23:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 22:08 [PATCH] - Pass OS logical cpu number to the SN prom (bios) Jack Steiner
2006-04-27 23:54 ` Keith Owens [this message]
2006-04-28  1:01 ` Jack Steiner

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=15771.1146182076@ocs3.ocs.com.au \
    --to=kaos@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox