All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elad Lahav <elahav@uwaterloo.ca>
To: sparclinux@vger.kernel.org
Subject: Processor IDs on the Niagara
Date: Fri, 12 Sep 2008 21:10:50 +0000	[thread overview]
Message-ID: <48CADADA.7050604@uwaterloo.ca> (raw)

I have a question regarding the meaning of cpu_data.proc_id.
My T1000 contains a single T1 processor, with 8 cores and 4 threads per core. The core_id 
value for each hardware thread is set up properly (though starting from 1 rather than 0). 
The proc_id value, however, does not make sense: it maps to core_id - 1. I would have 
expected one of two values:
1. The virtual processor ID, as described in the Machine Description block ("cpu"->"id");
2. A physical processor ID, shared by all 32 threads (and differs among chips on the T2+).
While the former is probably the same as the kernel's CPU id, the latter, so I believe, 
should be part of cpu_data.

A side effect of this issue is that cpu_sibling_map and cpu_core_map are the same (though 
this may be the expected result, I'm not sure).

Here are the per-virtual-processor values on my machine. The format is
CPUID proc_id core_id (sibling map) (core map)

00 00 01 (00,01,02,03) (00,01,02,03)
01 00 01 (00,01,02,03) (00,01,02,03)
02 00 01 (00,01,02,03) (00,01,02,03)
03 00 01 (00,01,02,03) (00,01,02,03)
04 01 02 (04,05,06,07) (04,05,06,07)
05 01 02 (04,05,06,07) (04,05,06,07)
06 01 02 (04,05,06,07) (04,05,06,07)
07 01 02 (04,05,06,07) (04,05,06,07)
08 02 03 (08,09,10,11) (08,09,10,11)
09 02 03 (08,09,10,11) (08,09,10,11)
10 02 03 (08,09,10,11) (08,09,10,11)
11 02 03 (08,09,10,11) (08,09,10,11)
12 03 04 (12,13,14,15) (12,13,14,15)
13 03 04 (12,13,14,15) (12,13,14,15)
14 03 04 (12,13,14,15) (12,13,14,15)
15 03 04 (12,13,14,15) (12,13,14,15)
16 04 05 (16,17,18,19) (16,17,18,19)
17 04 05 (16,17,18,19) (16,17,18,19)
18 04 05 (16,17,18,19) (16,17,18,19)
19 04 05 (16,17,18,19) (16,17,18,19)
20 05 06 (20,21,22,23) (20,21,22,23)
21 05 06 (20,21,22,23) (20,21,22,23)
22 05 06 (20,21,22,23) (20,21,22,23)
23 05 06 (20,21,22,23) (20,21,22,23)
24 06 07 (24,25,26,27) (24,25,26,27)
25 06 07 (24,25,26,27) (24,25,26,27)
26 06 07 (24,25,26,27) (24,25,26,27)
27 06 07 (24,25,26,27) (24,25,26,27)
28 07 08 (28,29,30,31) (28,29,30,31)
29 07 08 (28,29,30,31) (28,29,30,31)
30 07 08 (28,29,30,31) (28,29,30,31)
31 07 08 (28,29,30,31) (28,29,30,31)

Elad

             reply	other threads:[~2008-09-12 21:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 21:10 Elad Lahav [this message]
2008-09-12 21:44 ` Processor IDs on the Niagara David Miller
2008-09-13  0:47 ` Elad Lahav
2008-09-13  0:53 ` Elad Lahav
2008-09-13  1:01 ` David Miller
2008-09-13  1:02 ` David Miller
2008-09-13  1:18 ` David Miller
2008-09-13  1:27 ` Elad Lahav
2008-09-13  1:38 ` David Miller
2008-09-15 21:26 ` Elad Lahav
2008-09-15 22:09 ` David Miller
2008-09-16 18:47 ` Elad Lahav
2008-09-16 18:48 ` David Miller
2008-09-17 18:45 ` Elad Lahav
2008-10-05 20:47 ` David Miller
2008-10-05 20:57 ` David Miller
2008-10-06 13:15 ` Elad Lahav

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=48CADADA.7050604@uwaterloo.ca \
    --to=elahav@uwaterloo.ca \
    --cc=sparclinux@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.