From: Chris Wright <chrisw@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Nathan Lynch <nathanl@austin.ibm.com>,
ashok.raj@intel.com, linux-kernel@vger.kernel.org, ak@muc.de,
zwane@arm.linux.org.uk, rusty@rustycorp.com.au, vatsa@in.ibm.com,
jschopp@austin.ibm.com, anil.s.keshavamurthy@intel.com
Subject: Re: Documentation for CPU hotplug support
Date: Tue, 15 Nov 2005 12:30:33 -0800 [thread overview]
Message-ID: <20051115203033.GF7991@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20051111175953.7a5ce8dd.akpm@osdl.org>
* Andrew Morton (akpm@osdl.org) wrote:
> Nathan Lynch <nathanl@austin.ibm.com> wrote:
> >
> > Argh, no. That current_in_cpuhotplug hack has to go.
>
> Yes, Ashok is busily working on removing that ;)
That's nice. As it is, it deadlocks on boot:
cpufreq_stats_init
lock_cpu_hotplug
cpufreq_stat_cpu_callback
... (trace below)
cpufreq_governor_performance
__cpufreq_driver_target
lock_cpu_hotplug <-- uh-oh
SysRq : Show State
sibling
task PC pid father child younger older
swapper D 003D08BC 764 1 0 2 (L-TLB)
eff8ed78 ef832030 c184a5f0 003d08bc effc5180 000000d0 df810b00 003d08bc
00000002 ef832030 c184a5a0 00000000 df810b00 003d08bc ef832030 eff8dab0
eff8dbd8 c0637140 c0637148 00000282 eff8edb0 c058bad3 eff8dab0 00000001
Call Trace:
[<c058bad3>] __down+0x76/0xde
[<c058a4aa>] __down_failed+0xa/0x10
[<c04609ef>] .text.lock.cpufreq+0xee/0x1ff
[<c0461049>] cpufreq_governor_performance+0x5d/0x74
[<c045ff1c>] __cpufreq_governor+0x70/0x106
[<c04603d8>] __cpufreq_set_policy+0x214/0x2b9
[<c04605db>] cpufreq_update_policy+0xca/0xf1
[<c0460fd5>] cpufreq_stat_cpu_callback+0x27/0x3e
[<c06f657d>] cpufreq_stats_init+0xf0/0x152
[<c06d59c2>] do_initcalls+0x56/0xba
[<c06d5a4a>] do_basic_setup+0x24/0x2a
[<c01003cf>] init+0xb5/0x1fe
[<c010148d>] kernel_thread_helper+0x5/0xb
next prev parent reply other threads:[~2005-11-15 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 15:59 Documentation for CPU hotplug support Ashok Raj
2005-11-10 16:56 ` Joel Schopp
2005-11-11 7:23 ` Nathan Lynch
2005-11-12 0:06 ` Paul Jackson
2005-11-12 1:59 ` Andrew Morton
2005-11-12 20:54 ` Zwane Mwaikambo
2005-11-15 20:30 ` Chris Wright [this message]
2005-11-23 17:40 ` Ashok Raj
-- strict thread matches above, loose matches on Subject: below --
2005-11-12 21:56 Raj, Ashok
2005-11-14 0:42 ` Zwane Mwaikambo
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=20051115203033.GF7991@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.com \
--cc=rusty@rustycorp.com.au \
--cc=vatsa@in.ibm.com \
--cc=zwane@arm.linux.org.uk \
/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