From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Anton Blanchard <anton@samba.org>
Cc: Andre Detsch <adetsch@br.ibm.com>,
cbe-oss-dev@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] [RFC] cell: saving spus information for kexec crash
Date: Mon, 14 May 2007 08:14:01 +1000 [thread overview]
Message-ID: <1179094441.32247.68.camel@localhost.localdomain> (raw)
In-Reply-To: <20070511172233.GA14587@kryten>
On Fri, 2007-05-11 at 12:22 -0500, Anton Blanchard wrote:
> 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.
That's interesting: We do have a dump_task_altivec() but it looks like
its never called ... ouch. Maybe we can use the XFPREGS stuff or should
we add our own hook in binfmt_elf.c for that ?
As for SPU state, there's code to dump the SPEs in a separate section,
though I don't know if it's been merged yet (no up to date git tree
at hand right now). It uses different macros off binfmt_elf.
Ben.
prev parent reply other threads:[~2007-05-13 22:14 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
2007-05-13 22:14 ` Benjamin Herrenschmidt [this message]
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=1179094441.32247.68.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=adetsch@br.ibm.com \
--cc=anton@samba.org \
--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).