linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Is Pandaboard cpuhotplug working stably?
Date: Tue, 3 Jan 2012 17:21:59 +0000	[thread overview]
Message-ID: <20120103172159.GB2914@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4EF94E5C.5040608@nvidia.com>

On Tue, Dec 27, 2011 at 10:19:32AM +0530, Varun Wadekar wrote:
> >>
> >> [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].

Either we deem the fix for [1] to have caused a worse problem than it
fixed and we back it out, or the patch in [2] gets merged.

Which happens depends on the scheduler people; it can only be solved by
solving the nigh-on impossible-to-satisfy demands of the scheduler code
upon the CPU hotplug code.

I would suggest that [2] is a rather important patch which needs to be
merged before -final.

      reply	other threads:[~2012-01-03 17:21 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
2012-01-03 17:21             ` Russell King - ARM Linux [this message]

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=20120103172159.GB2914@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).