From: Andi Kleen <ak@muc.de>
To: YhLu <YhLu@tyan.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way
Date: 2 Jun 2005 20:51:53 +0200
Date: Thu, 2 Jun 2005 20:51:53 +0200 [thread overview]
Message-ID: <20050602185153.GG1683@muc.de> (raw)
In-Reply-To: <3174569B9743D511922F00A0C94314230A403903@TYANWEB>
On Wed, Jun 01, 2005 at 08:26:00PM -0700, YhLu wrote:
> Brought up 4 CPUs
> CPU 0, cpu_sibling_map[0]= 1
> CPU 0, cpu_core_map[0]= 3
> CPU 1, cpu_sibling_map[1]= 2
> CPU 1, cpu_core_map[1]= 3
> CPU 2, cpu_sibling_map[2]= 4
> CPU 2, cpu_core_map[2]= c
> CPU 3, cpu_sibling_map[3]= 8
> CPU 3, cpu_core_map[3]= c
> are the cpu_sibling_map[] right?
Yes it is correct. A CPU is always a sibling of itself.
-Andi
next prev parent reply other threads:[~2005-06-02 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 3:26 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way YhLu
2005-06-02 18:51 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 21:34 YhLu
2005-06-02 21:33 YhLu
2005-06-03 16:12 ` Andi Kleen
2005-06-02 21:15 YhLu
2005-06-02 20:42 YhLu
2005-06-03 16:09 ` Andi Kleen
2005-06-03 18:56 ` Siddha, Suresh B
2005-06-02 18:56 YhLu
2005-06-02 19:03 ` Dave Jones
2005-06-03 19:26 ` Siddha, Suresh B
2005-06-02 19:06 ` Ashok Raj
2005-06-02 18:55 YhLu
2005-06-02 3:16 YhLu
2005-06-02 18:50 ` Andi Kleen
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=20050602185153.GG1683@muc.de \
--to=ak@muc.de \
--cc=YhLu@tyan.com \
--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