linux-hexagon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: rkuo@codeaurora.org, tglx@linutronix.de, linas@codeaurora.org,
	mingo@elte.hu, a.p.zijlstra@chello.nl, dhowells@redhat.com,
	yasutake.koichi@jp.panasonic.com, akpm@linux-foundation.org,
	benh@kernel.crashing.org, jesper.nilsson@axis.com,
	cmetcalf@tilera.com, linux@arm.linux.org.uk,
	jejb@parisc-linux.org, deller@gmx.de, vapier@gentoo.org
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-am33-list@redhat.com, linux-parisc@vger.kernel.org
Subject: [PATCH 0/4] arch/CPU hotplug: Add missing CPU Hotplug bits to fix nasty issues
Date: Thu, 22 Mar 2012 16:58:00 +0530	[thread overview]
Message-ID: <20120322112735.17063.21791.stgit@srivatsabhat.in.ibm.com> (raw)

Unfortunately, some of the CPU Hotplug code has been duplicated in all of
the architectures. And in some cases, very poorly (some architectures left
out some of the important bits), to add to the woes.

Commit 5fbd036b552f633abb394a319f7c62a5c86a9cd7 (sched: Cleanup cpu_active
madness) introduced some changes that made the scheduler rely on the
CPU_STARTING notifier. And hence those architectures which forgot to
send out the CPU_STARTING notification will almost surely get into trouble.
(Xen is one example[1]).

The proper fix would be to pull out these bits into generic CPU Hotplug code.
But for now, fix this regression by adding the missing bits in the respective
architectures.

[1].https://lkml.org/lkml/2012/3/20/459
--
 Srivatsa S. Bhat (4):
      hexagon/CPU hotplug: Add missing call to notify_cpu_starting()
      mn10300/CPU hotplug: Add missing call to notify_cpu_starting()
      parisc/CPU hotplug: Add missing call to notify_cpu_starting()
      tile/CPU hotplug: Add missing call to notify_cpu_starting()


  arch/hexagon/kernel/smp.c  |    5 +++++
 arch/mn10300/kernel/smp.c  |    8 ++++++--
 arch/parisc/kernel/smp.c   |    7 ++++++-
 arch/tile/kernel/smpboot.c |    2 ++
 4 files changed, 19 insertions(+), 3 deletions(-)


Regards,
Srivatsa S. Bhat
IBM Linux Technology Center

             reply	other threads:[~2012-03-22 11:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 11:28 Srivatsa S. Bhat [this message]
2012-03-22 11:28 ` [PATCH 1/4] hexagon/CPU hotplug: Add missing call to notify_cpu_starting() Srivatsa S. Bhat
2012-04-03 21:09   ` Richard Kuo
2012-03-22 11:28 ` [PATCH 2/4] mn10300/CPU " Srivatsa S. Bhat
2012-03-22 11:28 ` [PATCH 3/4] parisc/CPU " Srivatsa S. Bhat
2012-03-22 11:29 ` [PATCH 4/4] tile/CPU " Srivatsa S. Bhat
2012-04-03 19:48   ` Chris Metcalf
2012-03-22 12:13 ` [PATCH 0/4] arch/CPU hotplug: Add missing CPU Hotplug bits to fix nasty issues Peter Zijlstra
2012-03-22 12:32   ` Peter Zijlstra
2012-03-22 14:53   ` James Bottomley
2012-03-22 14:55     ` Peter Zijlstra

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=20120322112735.17063.21791.stgit@srivatsabhat.in.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=cmetcalf@tilera.com \
    --cc=deller@gmx.de \
    --cc=dhowells@redhat.com \
    --cc=jejb@parisc-linux.org \
    --cc=jesper.nilsson@axis.com \
    --cc=linas@codeaurora.org \
    --cc=linux-am33-list@redhat.com \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@elte.hu \
    --cc=rkuo@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=vapier@gentoo.org \
    --cc=yasutake.koichi@jp.panasonic.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).