From: Matt Sealey <matt@genesi-usa.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] add Altivec/VMX state to coredumps
Date: Tue, 25 Sep 2007 19:00:26 +0100 [thread overview]
Message-ID: <46F94CBA.2060901@genesi-usa.com> (raw)
In-Reply-To: <E4CA12E1-888D-4A8B-B687-02F9D2850E1F@kernel.crashing.org>
Kumar Gala wrote:
> On Sep 24, 2007, at 11:03 PM, Mark Nelson wrote:
>
>> Update dump_task_altivec() (that has so far never been put to use)
>> so that it dumps the Altivec/VMX registers (VR[0] - VR[31], VSCR
>> and VRSAVE) in the same format as the ptrace get_vrregs() and add
>> the appropriate glue typedefs and #defines to
>> include/asm-powerpc/elf.h for it to work.
>
> Is there some way to tell if the core dump has altivec registers
> state in it?
>
> I'm wondering how we distinguish a core dump w/altivec state vs one
> with SPE state.
Sheer number of registers saved?
Why not put the PVR in core dumps that'd make it all easier..
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2007-09-25 17:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 4:03 [PATCH] add Altivec/VMX state to coredumps Mark Nelson
2007-09-25 12:39 ` Kumar Gala
2007-09-25 18:00 ` Matt Sealey [this message]
2007-09-25 22:18 ` Benjamin Herrenschmidt
2007-09-26 11:05 ` Matt Sealey
2007-09-26 13:21 ` Segher Boessenkool
2007-09-26 13:32 ` Kumar Gala
2007-09-26 13:38 ` Segher Boessenkool
2007-09-26 14:00 ` Matt Sealey
2007-09-26 1:22 ` Mark Nelson
2007-09-26 3:56 ` Kumar Gala
2007-09-26 4:56 ` Mark Nelson
2007-09-26 5:37 ` Kumar Gala
2007-09-26 7:42 ` Geert Uytterhoeven
2007-09-27 2:53 ` Michael Ellerman
2007-09-27 2:48 ` Michael Ellerman
2007-09-27 10:10 ` Kumar Gala
2007-09-27 23:54 ` 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=46F94CBA.2060901@genesi-usa.com \
--to=matt@genesi-usa.com \
--cc=galak@kernel.crashing.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 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.