From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: smp: Fix the CPU hotplug race with scheduler.
Date: Tue, 21 Jun 2011 15:47:04 +0530 [thread overview]
Message-ID: <4E006FA0.7050508@ti.com> (raw)
In-Reply-To: <20110621100057.GB23802@n2100.arm.linux.org.uk>
On 6/21/2011 3:30 PM, Russell King - ARM Linux wrote:
> On Tue, Jun 21, 2011 at 02:38:34PM +0530, Santosh Shilimkar wrote:
>> Russell,
>>
>> On 6/20/2011 8:24 PM, Santosh Shilimkar wrote:
>>> On 6/20/2011 7:53 PM, Russell King - ARM Linux wrote:
>>>> So, as loops_per_jiffy is not local to this function, the compiler has
>>>> to write out that zero value, before calling calibrate_delay_converge(),
>>>> and loops_per_jiffy only becomes non-zero _after_
>>>> calibrate_delay_converge()
>>>> has returned. This opens the window and allows the spinlock debugging
>>>> code to explode.
>>>>
>>>> This patch closes the window completely, by only writing to
>>>> loops_per_jiffy
>>>> only when we have a real value for it.
>>>>
>>>> This allows me to boot 3.0.0-rc3 on Versatile Express (4 CPU) whereas
>>>> without this it fails with spinlock lockup and rcu problems.
>>>>
>>>> init/calibrate.c | 14 ++++++++------
>>>> 1 files changed, 8 insertions(+), 6 deletions(-)
>>>>
>>> I am away from my board now. Will test this change.
>> Have tested your change and it seems to fix the crash I
>> was observing. Are you planning to send this fix for rc5?
>
> Yes. I think sending CPUs into infinite loops in the spinlock code is
> definitely sufficiently serious that it needs to go to Linus ASAP.
> It'd be nice to have a tested-by line though.
>
Sure.
>>> btw, the online-active race is still open even with this patch close
>>> and should be fixed.
>>>
>> The only problem remains is waiting for active mask before
>> marking CPU online. Shall I refresh my patch with only
>> this change then ?
>
> I already have that as a separate change.
Can you point me to both of these commits so that I have
them in my tree for testing.
Thanks for help.
Regards
Santosh
next prev parent reply other threads:[~2011-06-21 10:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 9:23 [RFC PATCH] ARM: smp: Fix the CPU hotplug race with scheduler Santosh Shilimkar
2011-06-20 9:50 ` Russell King - ARM Linux
2011-06-20 10:14 ` Russell King - ARM Linux
2011-06-20 10:28 ` Santosh Shilimkar
2011-06-20 10:35 ` Russell King - ARM Linux
2011-06-20 10:45 ` Santosh Shilimkar
2011-06-20 11:42 ` Santosh Shilimkar
2011-06-20 10:44 ` Russell King - ARM Linux
2011-06-20 10:47 ` Santosh Shilimkar
2011-06-20 11:13 ` Russell King - ARM Linux
2011-06-20 11:25 ` Santosh Shilimkar
2011-06-20 11:40 ` Russell King - ARM Linux
2011-06-20 11:51 ` Santosh Shilimkar
2011-06-20 12:19 ` Russell King - ARM Linux
2011-06-20 12:27 ` Santosh Shilimkar
2011-06-20 12:57 ` Russell King - ARM Linux
2011-06-20 14:23 ` Russell King - ARM Linux
2011-06-20 14:54 ` Santosh Shilimkar
2011-06-20 15:01 ` Russell King - ARM Linux
2011-06-20 15:10 ` Santosh Shilimkar
2011-06-21 9:08 ` Santosh Shilimkar
2011-06-21 10:00 ` Russell King - ARM Linux
2011-06-21 10:17 ` Santosh Shilimkar [this message]
2011-06-21 10:19 ` Russell King - ARM Linux
2011-06-21 10:21 ` Santosh Shilimkar
2011-06-21 10:26 ` Russell King - ARM Linux
2011-06-21 20:16 ` Stephen Boyd
2011-06-21 23:10 ` Russell King - ARM Linux
2011-06-22 0:06 ` Stephen Boyd
2011-06-22 10:06 ` Russell King - ARM Linux
2011-06-20 10:19 ` Santosh Shilimkar
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=4E006FA0.7050508@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).