From: Haren Myneni <haren@us.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd.bergmann@de.ibm.com>,
cbe-oss-dev@ozlabs.org
Subject: Re: [PATCH 1/2] Add support for stopping spus from xmon
Date: Thu, 12 Oct 2006 20:10:35 -0700 [thread overview]
Message-ID: <452F03AB.7030505@us.ibm.com> (raw)
In-Reply-To: <20061012120310.6B5A967BD5@ozlabs.org>
Michael Ellerman wrote:
>This patch adds support for stopping, and restarting, spus
>from xmon. We use the spu master runcntl bit to stop execution,
>this is apparently the "right" way to control spu execution and
>spufs will be changed in the future to use this bit.
>
>Testing has shown that to restart execution we have to turn the
>master runcntl bit on and also rewrite the spu runcntl bit, even
>if it is already set to 1 (running).
>
>Stopping spus is triggered by the xmon command 'ss' - "spus stop"
>perhaps. Restarting them is triggered via 'sr'. Restart doesn't
>start execution on spus unless they were running prior to being
>stopped by xmon.
>
>Walking the spu->full_list in xmon after a panic, would mean
>corruption of any spu struct would make all the others
>inaccessible. To avoid this, and also to make the next patch
>easier, we cache pointers to all spus during boot.
>
>We attempt to catch and recover from errors while stopping and
>restarting the spus, but as with most xmon functionality there are
>no guarantees that performing these operations won't crash xmon
>itself.
>
>
>
I think, kdump also need stop_spus() functionality when the dump support
is included on cell. If so, how about both stop_spus() and start_spus()
in platforms/cell/.
Thanks
Haren
next prev parent reply other threads:[~2006-10-13 3:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 12:03 [PATCH 0/2] Cell xmon helpers Michael Ellerman
2006-10-12 12:03 ` [PATCH 1/2] Add support for stopping spus from xmon Michael Ellerman
2006-10-12 16:18 ` Linas Vepstas
2006-10-18 7:13 ` Michael Ellerman
2006-10-13 3:10 ` Haren Myneni [this message]
2006-10-18 7:16 ` Michael Ellerman
2006-10-13 3:18 ` Luke Browning
2006-10-18 7:14 ` Michael Ellerman
2006-10-12 12:03 ` [PATCH 2/2] Add support for dumping spu info " Michael Ellerman
2006-10-12 17:42 ` [Cbe-oss-dev] " Geoff Levand
2006-10-18 6:56 ` Michael Ellerman
2006-11-10 9:11 ` Geoff Levand
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=452F03AB.7030505@us.ibm.com \
--to=haren@us.ibm.com \
--cc=arnd.bergmann@de.ibm.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).