From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Cc: Andre Detsch <adetsch@br•ibm.com>,
Anton Blanchard <anton@samba•org>,
cbe-oss-dev@ozlabs•org
Subject: Re: [RFC] cell: saving spus information for kexec crash
Date: Fri, 11 May 2007 19:48:12 +0200 [thread overview]
Message-ID: <200705111948.12664.arnd@arndb.de> (raw)
In-Reply-To: <20070511172233.GA14587@kryten>
On Friday 11 May 2007, Anton Blanchard wrote:
> > This patch adds support for investigating spus information after a
> > kernel crash event, through kdump vmcore file.
> > Implementation is based on xmon code, but the new functionality was
> > kept independent.
>
> This brings up a point: it looks like kdump doesnt capture the FP and
> altivec regs. Could be important for some bugs.
Yes, and there are more things that might be worth adding:
- SLB contents (as noticed by Luke Browning)
- some SPRs
- state of some device drivers
We have briefly discussed the idea of having generic notifiers into
which arbitrary subsystems can register, but unless we have more than
one or two users, it's probably not worth it.
> This brings up yet another point, it looks like our userspace core dumps
> dont capture altivec or SPU state.
Actually, the userspace core dumps do capture the SPU state as of 2.6.21,
thanks to the work of Dwayne McConnell :-)
Arnd <><
next prev parent reply other threads:[~2007-05-11 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705111353.22781.adetsch@br.ibm.com>
2007-05-11 17:22 ` [RFC] cell: saving spus information for kexec crash Anton Blanchard
2007-05-11 17:48 ` Arnd Bergmann [this message]
2007-05-13 22:14 ` [Cbe-oss-dev] " Benjamin Herrenschmidt
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=200705111948.12664.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=adetsch@br$(echo .)ibm.com \
--cc=anton@samba$(echo .)org \
--cc=cbe-oss-dev@ozlabs$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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