From: Kevin Cernekee <cernekee@gmail.com>
To: Michael Bohan <mbohan@codeaurora.org>
Cc: mingo@elte.hu, akpm@linux-foundation.org,
simon.kagstrom@netinsight.net, David.Woodhouse@intel.com,
lethal@linux-sh.org, tj@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, "Shilimkar,
Santosh" <santosh.shilimkar@ti.com>
Subject: Re: console_cpu_notify can cause scheduling BUG during CPU hotplug
Date: Mon, 25 Apr 2011 17:18:37 -0700 [thread overview]
Message-ID: <BANLkTimPHaiiiVC_A6jtUtaa_pYJuhepYg@mail.gmail.com> (raw)
In-Reply-To: <4DB604C7.8090305@codeaurora.org>
On Mon, Apr 25, 2011 at 4:33 PM, Michael Bohan <mbohan@codeaurora.org> wrote:
> I was curious if this scenario was accounted for in the design of the
> console CPU notifier. One workaround for this problem is to remove CPU_DEAD
> from the possible actions in console_cpu_notify(). In fact, v1-v4 of the
> patch above did not have CPU_DEAD, CPU_DYING or CPU_DOWN_FAILED in the list
> of actions. I wasn't able to track down why the other cases were added in
> the final patch.
Here is the background information on the CPU_{DEAD,DYING,DOWN_FAILED} cases:
http://lkml.org/lkml/2010/6/29/65
next prev parent reply other threads:[~2011-04-26 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 23:33 console_cpu_notify can cause scheduling BUG during CPU hotplug Michael Bohan
2011-04-26 0:18 ` Kevin Cernekee [this message]
2011-04-26 5:58 ` Santosh Shilimkar
2011-04-26 21:06 ` Michael Bohan
2011-04-27 7:38 ` Borislav Petkov
2011-04-27 22:12 ` Michael Bohan
2011-04-30 8:38 ` Borislav Petkov
2011-05-09 20:39 ` Michael Bohan
-- strict thread matches above, loose matches on Subject: below --
2011-08-30 8:37 Shen Canquan
2011-09-05 8:34 ` canquan.shen
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=BANLkTimPHaiiiVC_A6jtUtaa_pYJuhepYg@mail.gmail.com \
--to=cernekee@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbohan@codeaurora.org \
--cc=mingo@elte.hu \
--cc=santosh.shilimkar@ti.com \
--cc=simon.kagstrom@netinsight.net \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).