From: Michael Ellerman <michael@ellerman.id.au>
To: Nathan Lynch <ntl@pobox.com>
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: Wed, 05 Apr 2006 13:23:30 +0200 [thread overview]
Message-ID: <1144236210.6788.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060404172550.GE25663@localdomain>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
On Tue, 2006-04-04 at 12:25 -0500, Nathan Lynch wrote:
> Michael Ellerman wrote:
> > Currently we use a cpumask called of_spin_map to keep track of which threads
> > have been spun up. We basically guess that OF has spun up all even numbered
> > threads, and so all the odd numbered threads need to be brought up.
> >
> > That's a bit of a dicey assumption at best, and is totally incorrect for
> > kexec.
> >
> > Luckily we have an rtas call which can tell us whether a cpu is up
> > or not, so let's use it?
>
> 1. query-cpu-stopped-state isn't available on all RTAS systems (I
> believe it's required only on systems that support cpu offline).
That should be ok, I'm pretty sure the way I've written it if
query-cpu-stopped-state isn't there we try and start it the old way
anyway.
> 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?
> 3. This isn't how query-cpu-stopped-state was intended to be used.
> It's meant to be used by the OS to determine when a thread has
> stopped itself using the stop-self method. Which might partially
> explain (2).
Perhaps, PAPR says: "The query-cpu-stopped-state primitive is used to
query a different processor thread to determine its status with respect
to the RTAS stopped state". I guess I assumed that a thread that's not
started would be in the "RTAS stopped state", which seems logical if not
correct.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-05 11:23 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 [this message]
2006-04-07 1:10 ` Nathan Lynch
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=1144236210.6788.6.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=arnd.bergmann@de.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.