From: Andi Kleen <ak@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: 2.6.16rc5 'found' an extra CPU.
Date: Thu, 2 Mar 2006 01:55:46 +0100 [thread overview]
Message-ID: <200603020155.46534.ak@suse.de> (raw)
In-Reply-To: <20060301230317.GF1440@redhat.com>
On Thursday 02 March 2006 00:03, Dave Jones wrote:
> On Wed, Mar 01, 2006 at 05:46:47PM -0500, Dave Jones wrote:
> > This amused me.
> >
> > (17:43:34:davej@nemesis:~)$ ll /proc/acpi/processor/
> > total 0
> > dr-xr-xr-x 2 root root 0 Mar 1 17:43 CPU1/
> > dr-xr-xr-x 2 root root 0 Mar 1 17:43 CPU2/
> > dr-xr-xr-x 2 root root 0 Mar 1 17:43 CPU3/
> > (17:43:36:davej@nemesis:~)$
>
> Digging further. I notice more oddities (or maybe I've just
> misunderstood this -- corrections welcomed)
Probably related to Ashok's ACPI CPU hotplug patches.
What's the full bootup log?
> (17:59:02:davej@nemesis:~)$ cat
> /sys/devices/system/cpu/cpu0/topology/core_id 0
> (17:59:23:davej@nemesis:~)$ cat
> /sys/devices/system/cpu/cpu1/topology/core_id 0
>
> (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 ?
It looks like a standard dual socket machine. Each CPU is a sibling of its own
only.
-Andi
next prev parent reply other threads:[~2006-03-02 0:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 22:46 Dave Jones
2006-03-01 23:03 ` Dave Jones
2006-03-02 0:55 ` Andi Kleen [this message]
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
2006-03-01 23:01 Moore, Robert
2006-03-02 0:55 Chuck Ebbert
2006-03-02 1:09 ` Dave Jones
2006-03-05 0:42 ` Andrew Morton
2006-03-05 2:26 ` Dave Jones
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 17:41 ` Ashok Raj
2006-03-02 17:30 Brown, Len
2006-03-02 17:34 Brown, Len
2006-03-02 19:16 Brown, Len
2006-03-02 19:18 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:37 Brown, Len
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=200603020155.46534.ak@suse.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome