public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Peter Rival <frival@zk3.dec.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	trini@kernel.crashing.org, benh@kernel.crashing.org
Subject: Re: [PATCH] change name of rep_nop
Date: Sat, 6 Oct 2001 09:28:17 +1000 (EST)	[thread overview]
Message-ID: <15294.16913.2117.383987@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <3BBDF6BC.5000300@zk3.dec.com>
In-Reply-To: <E15pW6U-0006Xx-00@the-village.bc.nu> <3BBDF6BC.5000300@zk3.dec.com>

Peter Rival writes:

> You also need to move the call to smp_boot_cpus() below the 
> clear_bit(...) line in smp_init().  Without it, my Wildfire doesn't get 

No, that won't work for me, because cpu_online_map is set by
smp_boot_cpus(), at least on PPC (in fact each CPU sets its bit in
cpu_online_map as it spins up).

There shouldn't be a race on x86 at all, because the secondary
processors don't call init_idle until after they see that the primary
cpu has call smp_commence.  (There is currently a race on PPC since we
call init_idle before waiting for smp_commence, but that would not be
your problem.)

> past the while(wait_init_idle) loop - seems all of the CPUs have already 
> done their work before the mask is set.  Besides, it's the right place 
> for it anyway.

No, I think it should be smp_boot_cpus, set wait_init_idle,
smp_commence, then the secondaries start clearing their bits.  Which
AFAICS is the way it is on x86.  What architecture is your wildfire?

Paul.

  reply	other threads:[~2001-10-05 23:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 10:46 [PATCH] change name of rep_nop Paul Mackerras
2001-10-05 14:37 ` Alan Cox
2001-10-05 18:06   ` Peter Rival
2001-10-05 23:28     ` Paul Mackerras [this message]
2001-10-05 23:54       ` Martin J. Bligh
2001-10-06  1:40         ` Paul Mackerras
2001-10-08 19:27           ` Peter Rival
2001-10-08 22:36           ` David Woodhouse
2001-10-08 22:46             ` David S. Miller
2001-10-08 23:16               ` Alan Cox
2001-10-08 23:24                 ` Dave Jones
2001-10-08 23:30                   ` David S. Miller
2001-10-08 23:33                   ` Alan Cox
2001-10-09  5:01                   ` George Greer
2001-10-09 10:33                 ` Benjamin Herrenschmidt
2001-10-09 11:30                   ` Keith Owens
2001-10-09 12:13                     ` Benjamin Herrenschmidt
2001-10-09 12:15                     ` Alan Cox
2001-10-08 22:49             ` Alan Cox
2001-10-08 23:06             ` David Woodhouse
2001-10-08 23:08               ` David S. Miller
2001-10-08 23:42               ` David Woodhouse
2001-10-08 23:46                 ` David S. Miller
2001-10-08 23:46             ` Linus Torvalds
2001-10-09  0:03               ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-10-09  8:51 Etienne Lorrain
2001-10-09 11:30 ` Alan Cox

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=15294.16913.2117.383987@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=frival@zk3.dec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=trini@kernel.crashing.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