linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: tbr/decrementer and SMP -- do the cpus stay in sync?
Date: Tue, 19 Oct 2004 09:46:54 +1000	[thread overview]
Message-ID: <1098143214.30522.40.camel@gaston> (raw)
In-Reply-To: <41742E62.6060603@nortelnetworks.com>

On Tue, 2004-10-19 at 06:58, Chris Friesen wrote:
> I thought I remembered some discussion on this a while back, but I can't find it 
> in my archived messages or online, so here goes.
> 
> With SMP PowerPC machines (specifically the dual G5) we sync up the timebase 
> when we bring up the second CPU.  Are we guaranteed that they stay in sync after 
> that point, or will they drift?  If they drift, do we have any idea how much?

Yes. They have the same clock source. They won't drift.
Ben.

      reply	other threads:[~2004-10-18 23:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18 20:58 tbr/decrementer and SMP -- do the cpus stay in sync? Chris Friesen
2004-10-18 23:46 ` Benjamin Herrenschmidt [this message]

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=1098143214.30522.40.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).