All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: 76306.1226@compuserve.com, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, ak@suse.de,
	Ashok Raj <ashok.raj@intel.com>
Subject: Re: 2.6.16rc5 'found' an extra CPU.
Date: Sat, 4 Mar 2006 16:42:38 -0800	[thread overview]
Message-ID: <20060304164238.37d2ea49.akpm@osdl.org> (raw)
In-Reply-To: <20060302010953.GA19755@redhat.com>

Dave Jones <davej@redhat.com> wrote:
>
> On Wed, Mar 01, 2006 at 07:55:25PM -0500, Chuck Ebbert wrote:
>  > In-Reply-To: <20060301230317.GF1440@redhat.com>
>  > 
>  > On Wed, 1 Mar 2006 18:03:17, Dave Jones wrote:
>  > 
>  > > (17:59:38:davej@nemesis:~)$ cat /sys/devices/system/cpu/cpu0/topology/core_siblings
>  > > 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001
>  > > (17:59:47:davej@nemesis:~)$ cat /sys/devices/system/cpu/cpu1/topology/core_siblings
>  > > 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000002
>  > > 
>  > > Neither of these CPUs are HT / dual-core, so shouldn't these be the same ?
>  > 
>  > Those are bitmaps. 1 => only bit 0 is set => CPU 0 is all alone.
>  > 
>  > Did you really build a 256-CPU SMP kernel or is ACPI ignoring CONFIG_NR_CPUS
>  > or something?
> 
> Yes, it's =256.
> 

Is that the only way in which to trigger the bug?

If so, I'd be inclined to hold the fix back for 2.6.17.


From: Ashok Raj <ashok.raj@intel.com>

Local apic entries are only 8 bits, but it seemed to not be caught with u8
return value result in the check cpu_index >= NR_CPUS becomming always false.

drivers/acpi/processor_core.c: In function `acpi_processor_get_info':
drivers/acpi/processor_core.c:483: warning: comparison is always false due to limited range of data type

Signed-off-by: Ashok Raj <ashok.raj@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>
Cc: Dave Jones <davej@codemonkey.org.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
---

 drivers/acpi/processor_core.c |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diff -puN drivers/acpi/processor_core.c~acpi-signedness-fix-2 drivers/acpi/processor_core.c
--- 25/drivers/acpi/processor_core.c~acpi-signedness-fix-2	Fri Mar  3 16:25:09 2006
+++ 25-akpm/drivers/acpi/processor_core.c	Fri Mar  3 16:25:09 2006
@@ -382,7 +382,7 @@ static int acpi_processor_remove_fs(stru
 
 /* Use the acpiid in MADT to map cpus in case of SMP */
 #ifndef CONFIG_SMP
-#define convert_acpiid_to_cpu(acpi_id) (0xff)
+#define convert_acpiid_to_cpu(acpi_id) (-1)
 #else
 
 #ifdef CONFIG_IA64
@@ -395,7 +395,7 @@ static int acpi_processor_remove_fs(stru
 #define ARCH_BAD_APICID		(0xff)
 #endif
 
-static u8 convert_acpiid_to_cpu(u8 acpi_id)
+static int convert_acpiid_to_cpu(u8 acpi_id)
 {
 	u16 apic_id;
 	int i;
@@ -421,7 +421,7 @@ static int acpi_processor_get_info(struc
 	acpi_status status = 0;
 	union acpi_object object = { 0 };
 	struct acpi_buffer buffer = { sizeof(union acpi_object), &object };
-	u8 cpu_index;
+	int cpu_index;
 	static int cpu0_initialized;
 
 	ACPI_FUNCTION_TRACE("acpi_processor_get_info");
@@ -466,7 +466,7 @@ static int acpi_processor_get_info(struc
 	cpu_index = convert_acpiid_to_cpu(pr->acpi_id);
 
 	/* Handle UP system running SMP kernel, with no LAPIC in MADT */
-	if (!cpu0_initialized && (cpu_index == 0xff) &&
+	if (!cpu0_initialized && (cpu_index == -1) &&
 	    (num_online_cpus() == 1)) {
 		cpu_index = 0;
 	}
@@ -480,7 +480,7 @@ static int acpi_processor_get_info(struc
 	 *  less than the max # of CPUs. They should be ignored _iff
 	 *  they are physically not present.
 	 */
-	if (cpu_index >= NR_CPUS) {
+	if (cpu_index == -1) {
 		if (ACPI_FAILURE
 		    (acpi_processor_hotadd_init(pr->handle, &pr->id))) {
 			ACPI_ERROR((AE_INFO,
_


  reply	other threads:[~2006-03-05  0:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02  0:55 2.6.16rc5 'found' an extra CPU Chuck Ebbert
2006-03-02  1:09 ` Dave Jones
2006-03-05  0:42   ` Andrew Morton [this message]
2006-03-05  2:26     ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2006-03-02 19:37 Brown, Len
2006-03-02 19:26 Brown, Len
2006-03-02 19:31 ` Dave Jones
2006-03-02 19:33 ` Andi Kleen
2006-03-02 19:18 Brown, Len
2006-03-02 19:18 ` Brown, Len
2006-03-02 19:16 Brown, Len
2006-03-02 19:16 ` Brown, Len
2006-03-02 17:34 Brown, Len
2006-03-02 17:34 ` Brown, Len
2006-03-02 17:30 Brown, Len
2006-03-02 17:30 ` Brown, Len
2006-03-02  5:49 Brown, Len
2006-03-02  5:49 ` Brown, Len
2006-03-02  9:33 ` Romano Giannetti
2006-03-02 15:53   ` Zwane Mwaikambo
2006-03-02 15:58     ` Romano Giannetti
2006-03-02 12:14 ` Andi Kleen
2006-03-02 16:30 ` Ashok Raj
2006-03-02 18:44   ` Dave Jones
2006-03-02 19:21     ` Ashok Raj
2006-03-03  7:14       ` Andrew Morton
2006-03-03  7:14         ` Andrew Morton
2006-03-03 17:41         ` Ashok Raj
2006-03-01 23:01 Moore, Robert
2006-03-01 23:01 ` Moore, Robert
2006-03-01 22:46 Dave Jones
2006-03-01 23:03 ` Dave Jones
2006-03-02  0:55   ` Andi Kleen
2006-03-02  1:19     ` Dave Jones
2006-03-02  1:38       ` Andi Kleen
2006-03-02  3:13         ` Dave Jones
2006-03-02  3:24           ` Andi Kleen
2006-03-02  3:45             ` Dave Jones
2006-03-02  3:52         ` Ashok Raj
2006-03-02  4:11           ` Dave Jones

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=20060304164238.37d2ea49.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=ashok.raj@intel.com \
    --cc=davej@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --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 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.