From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix ppc32 smp build.
Date: Tue, 08 Nov 2005 08:20:36 +1100 [thread overview]
Message-ID: <1131398436.4652.57.camel@gaston> (raw)
In-Reply-To: <1131356850.27347.17.camel@baythorne.infradead.org>
On Mon, 2005-11-07 at 09:47 +0000, David Woodhouse wrote:
> On Sun, 2005-11-06 at 21:51 +1100, Paul Mackerras wrote:
> > If we really can get unsynchronized timebases still, then I suppose we
> > need to bring back the smp_tb_synchronized variable,
>
> We make no attempt to sync the timebases on quad powersurge, as far as I
> can tell -- and we never set smp_tb_synchronized there.
We don't even use the software sync ? Hrm... actually, I think the
software sync was designed for 2 CPUs only.
Now, go find the one user that had a quad powersurge :)
Ben.
next prev parent reply other threads:[~2005-11-07 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 8:00 [PATCH] Fix ppc32 smp build David Woodhouse
2005-11-06 10:51 ` Paul Mackerras
2005-11-07 9:47 ` David Woodhouse
2005-11-07 21:20 ` Benjamin Herrenschmidt [this message]
2005-11-07 23:29 ` Paul Mackerras
2005-11-08 1:38 ` Mark Guertin
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=1131398436.4652.57.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--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).