From: Nathan Lynch <ntl@pobox.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Arnd Bergmann <arnd.bergmann@de.ibm.com>
Subject: Re: [RFC/PATCH] powerpc: Use rtas query-cpu-stopped-state in smp spinup
Date: Thu, 6 Apr 2006 20:10:02 -0500 [thread overview]
Message-ID: <20060407011002.GF9208@localdomain> (raw)
In-Reply-To: <1144236210.6788.6.camel@localhost.localdomain>
Michael Ellerman wrote:
> On Tue, 2006-04-04 at 12:25 -0500, Nathan Lynch wrote:
>
> > 2. I've tried it before. Hope I'm remembering this correctly, but I
> > think my experience was that query-cpu-stopped-state reported
> > nonsense for cpus that were started by OF. This was on Power5,
> > btw.
>
> That's not what I see, perhaps I have newer firmware?
I tried your patch (non-kexec boot) on a 1-way SMT power5 with
2.6.17-rc1 and got the badness below, and I think it matches what I
ran into in the past. Maybe doing query-cpu-stopped-state on a thread
that has yet to be started by RTAS mucks things up?
Memory: 2047640k/2097152k available (5356k kernel code, 49512k
reserved, 1412k data, 900k bss, 240k init)
Calibrating delay loop... 375.80 BogoMIPS (lpj=751616)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 256
Processor 1 is stuck. <<<<<<<<
Brought up 1 CPUs
Node 0 CPUs: 0
migration_cost=0
next prev parent reply other threads:[~2006-04-07 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 11:24 [RFC/PATCH] powerpc: Use rtas query-cpu-stopped-state in smp spinup Michael Ellerman
2006-04-04 12:42 ` Anton Blanchard
2006-04-04 12:46 ` Michael Ellerman
2006-04-04 17:25 ` Nathan Lynch
2006-04-05 11:23 ` Michael Ellerman
2006-04-07 1:10 ` Nathan Lynch [this message]
2006-04-11 8:53 ` Michael Ellerman
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=20060407011002.GF9208@localdomain \
--to=ntl@pobox.com \
--cc=arnd.bergmann@de.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.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