From: Nick Piggin <nickpiggin@yahoo.com.au>
To: unlisted-recipients:; (no To-header on input)
Cc: Dave Hansen <haveblue@us.ibm.com>,
"Matthew C. Dobson [imap]" <colpatch@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sched domains bringup race?
Date: Fri, 16 Jul 2004 15:27:59 +1000 [thread overview]
Message-ID: <40F7675F.6090506@yahoo.com.au> (raw)
In-Reply-To: <40F74F9C.8080205@yahoo.com.au>
Nick Piggin wrote:
> Dave Hansen wrote:
>
>> On Thu, 2004-07-15 at 20:03, Nick Piggin wrote:
>>
>>> It shouldn't because sched_init sets up dummy domains for
>>> all runqueues.
>>>
>>> Obviously something is going wrong somewhere though.
>>
>>
>>
>> Hmmm, but there still might be some concurrency problems, right? There
>> isn't any locking while the setup is being done, so are all of the
>> intermediate initialization states valid? Or, could one of the CPUs be
>> catching the init code in the middle of an operation?
>>
>
> cpu_attach_domain is supposed to be able to do the switchover
> without any races.
Although the sched_domain_debug is definitely racy. It should really
be locking each runqueue before traversing its domains. Just undef
SCHED_DOMAIN_DEBUG to be sure...
next prev parent reply other threads:[~2004-07-16 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 2:13 sched domains bringup race? Dave Hansen
2004-07-16 3:03 ` Nick Piggin
2004-07-16 3:30 ` Dave Hansen
2004-07-16 3:46 ` Nick Piggin
2004-07-16 5:27 ` Nick Piggin [this message]
2004-07-18 20:45 ` Keshavamurthy Anil S
2004-07-19 7:31 ` Nick Piggin
2004-07-22 21:55 ` Nathan Lynch
2004-07-22 23:23 ` Keshavamurthy Anil S
2004-07-23 0:33 ` Nick Piggin
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=40F7675F.6090506@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=colpatch@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.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