From: Anton Blanchard <anton@samba.org>
To: Andre Detsch <adetsch@br.ibm.com>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org
Subject: Re: [RFC] cell: saving spus information for kexec crash
Date: Fri, 11 May 2007 12:22:33 -0500 [thread overview]
Message-ID: <20070511172233.GA14587@kryten> (raw)
In-Reply-To: <200705111353.22781.adetsch@br.ibm.com>
Hi,
> 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.
This brings up yet another point, it looks like our userspace core dumps
dont capture altivec or SPU state.
Anton
next parent reply other threads:[~2007-05-11 17:22 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 ` Anton Blanchard [this message]
2007-05-11 17:48 ` [RFC] cell: saving spus information for kexec crash Arnd Bergmann
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=20070511172233.GA14587@kryten \
--to=anton@samba.org \
--cc=adetsch@br.ibm.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).