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: 3 Jun 2005 18:12:25 +0200
Date: Fri, 3 Jun 2005 18:12:25 +0200 [thread overview]
Message-ID: <20050603161225.GI1683@muc.de> (raw)
In-Reply-To: <3174569B9743D511922F00A0C94314230A40399E@TYANWEB>
On Thu, Jun 02, 2005 at 02:33:06PM -0700, YhLu wrote:
> So siblings should be in one core...? that make sense....
Yes. The whole terminology is confusing for historical reasons.
If we started again with the naming game there would be probably
different names.
To make it even more confusing while it is different internally
in the kernel, CPUID and /proc/cpuinfo fake them to the same
to the world to be compatible with old software who e.g.
reads this for licensing purposes.
BTW I doubt these are related to the hang you are chasing
because if you grep the kernel cpu_core_map is never used
in the kernel at all except for cpuinfo. This means
it is unlikely to cause any hangs.
-Andi
next prev parent reply other threads:[~2005-06-03 16:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 21:33 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way YhLu
2005-06-03 16:12 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 21:34 YhLu
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:26 YhLu
2005-06-02 18:51 ` Andi Kleen
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=20050603161225.GI1683@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