From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Li Zhong <zhong@linux.vnet.ibm.com>
Cc: Paul Mackerras <paulus@samba.org>,
PowerPC email list <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH powerpc] Set cpu sibling mask before online cpu
Date: Tue, 11 Jun 2013 17:00:16 +1000 [thread overview]
Message-ID: <1370934016.8250.83.camel@pasglop> (raw)
In-Reply-To: <1368699626.2618.183.camel@ThinkPad-T5421>
On Thu, 2013-05-16 at 18:20 +0800, Li Zhong wrote:
> It seems following race is possible:
>
.../...
> vdso_getcpu_init();
> #endif
> - notify_cpu_starting(cpu);
> - set_cpu_online(cpu, true);
> /* Update sibling maps */
> base = cpu_first_thread_sibling(cpu);
> for (i = 0; i < threads_per_core; i++) {
> - if (cpu_is_offline(base + i))
> + if (cpu_is_offline(base + i) && (cpu != base + i))
> continue;
> cpumask_set_cpu(cpu, cpu_sibling_mask(base + i));
> cpumask_set_cpu(base + i, cpu_sibling_mask(cpu));
> @@ -667,6 +665,10 @@ __cpuinit void start_secondary(void *unused)
> }
> of_node_put(l2_cache);
>
> + smp_wmb();
> + notify_cpu_starting(cpu);
> + set_cpu_online(cpu, true);
> +
So we could have an online CPU with an empty sibling mask. Now we can
have a sibling that isn't online ... Is that ok ?
Or should we do a two pass mechanism:
- Pass 1, set the new cpu siblings
- set_cpu_online
- Pass 2, set other CPU sibling of this cpu
?
Cheers,
Ben.
next prev parent reply other threads:[~2013-06-11 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 10:20 [RFC PATCH powerpc] Set cpu sibling mask before online cpu Li Zhong
2013-06-11 7:00 ` Benjamin Herrenschmidt [this message]
2013-06-11 8:33 ` Srivatsa S. Bhat
2013-06-11 9:03 ` Benjamin Herrenschmidt
2013-06-13 9:42 ` Li Zhong
2013-06-11 8:35 ` Srivatsa S. Bhat
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=1370934016.8250.83.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=zhong@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).