From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andi Kleen <andi@firstfloor.org>
Cc: Chris Snook <csnook@redhat.com>, Zurk Tech <zurktech@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Quad core CPU detected but shows as single core in 2.6.23.1
Date: Sun, 04 Nov 2007 22:18:21 +0100 [thread overview]
Message-ID: <1194211101.20832.3.camel@lappy> (raw)
In-Reply-To: <p737ikx3ksn.fsf@bingen.suse.de>
On Sun, 2007-11-04 at 19:52 +0100, Andi Kleen wrote:
> Chris Snook <csnook@redhat.com> writes:
>
> >> Marking TSC unstable due to TSCs unsynchronized
> >
> > This is probably wrong. The TSC is on the northbridge on Barcelona
> > chips, so every core on the die should be in sync. Hypothetically you
> > could have different speed northbridges in different sockets, but
> > we've never tried very hard to support that case anyway. We should
> > probably be marking the TSC as stable on Barcelona chips.
>
> It's a little more complicated. Stable clock is only guaranteed as long
> as the CPUs all run on the same clock crystal. That is true
> when they're all on the current motherboard. But at least for K8
> there were several systems that consist of multiple motherboards
> and HT cables inbetween them (like all the 8 socket systems).
> On those the TSCs can drift too with Fam10h. I'm not aware
> of any of those shipping yet, but since it's essentially
> the same platform as K8 they will appear sooner or later.
>
> So far we lack a reliable way to detect this condition. If it could
> be detected it would be possible to switch to TSC timing
> for the single motherboard systems.
Would it not be as simple as looking at the BIOS provided topology
information? If nr sockets > 4 assume multiple board.
Of course one could run a multi board solution and not utilize all
sockets, in which case the heuristic would fail, but I guess buying such
an expensive solution and then not sticking in the cpus is rather rare.
next prev parent reply other threads:[~2007-11-04 21:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 19:31 Quad core CPU detected but shows as single core in 2.6.23.1 Zurk Tech
2007-11-04 1:32 ` Chris Snook
2007-11-04 18:52 ` Andi Kleen
2007-11-04 21:18 ` Peter Zijlstra [this message]
2007-11-04 23:07 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2007-10-25 14:50 Zurk Tech
2007-11-01 20:38 ` Andrew Morton
2007-11-01 22:55 ` Zurk Tech
2007-10-25 3:02 Zurk Tech
2007-10-25 3:06 ` Arjan van de Ven
2007-10-25 13:59 ` Zurk Tech
2007-10-25 3:34 ` Chris Snook
2007-10-25 14:11 ` Zurk Tech
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=1194211101.20832.3.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zurktech@gmail.com \
/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