From: vwadekar@nvidia•com (Varun Wadekar)
To: linux-arm-kernel@lists•infradead.org
Subject: Is Pandaboard cpuhotplug working stably?
Date: Tue, 27 Dec 2011 10:19:32 +0530 [thread overview]
Message-ID: <4EF94E5C.5040608@nvidia.com> (raw)
In-Reply-To: <20111222102454.GD3354@n2100.arm.linux.org.uk>
>> There are few patches floating around for this issue. I posted one version
>> long back [1] and then there was one more form Thomas G.
>> The most recent is from one is from Peter Z [2] which is moving the
>> fix for the cup online race to core code.
>>
>> Can you try Peter's patch with your test-case ?
>>
>> Regards,
>> Santosh
>>
>> [1] https://lkml.org/lkml/2011/6/20/79
>> [2] https://lkml.org/lkml/2011/12/15/255
> [1] is already fixed - and is not the latest "problem" with this code.
> Fixing the problem in [1] actually itself created the latest problem
> with smp_call_function() which wasn't there before this change. Patch
> [2] refers to this problem and proposes a fix for it.
>
>
Any idea if this patch if good to go in mainline? I am facing the same
issue on Tegra with 3.1.5 and this patch fixes the issue caused by [1].
Ideally if this change is ok, then it should be merged into 3.1.6 too.
Since this change seems to fix the issue at hand, I intend to merge the
change directly in our internal repo and wait for it to be a part of 3.1.6.
Thanks.
next prev parent reply other threads:[~2011-12-27 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 9:23 Is Pandaboard cpuhotplug working stably? Barry Song
2011-12-21 9:46 ` Russell King - ARM Linux
2011-12-21 9:59 ` Barry Song
2011-12-21 10:07 ` Russell King - ARM Linux
2011-12-22 8:49 ` Shilimkar, Santosh
2011-12-22 10:24 ` Russell King - ARM Linux
2011-12-22 10:27 ` Shilimkar, Santosh
2011-12-27 4:49 ` Varun Wadekar [this message]
2012-01-03 17:21 ` Russell King - ARM Linux
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=4EF94E5C.5040608@nvidia.com \
--to=vwadekar@nvidia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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