From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id AC2EADDDFE for ; Wed, 26 Sep 2007 08:20:36 +1000 (EST) Subject: Re: [PATCH] add Altivec/VMX state to coredumps From: Benjamin Herrenschmidt To: Matt Sealey In-Reply-To: <46F94CBA.2060901@genesi-usa.com> References: <46F88896.50706@au1.ibm.com> <46F94CBA.2060901@genesi-usa.com> Content-Type: text/plain Date: Wed, 26 Sep 2007 08:18:31 +1000 Message-Id: <1190758712.23457.0.camel@localhost.localdomain> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2007-09-25 at 19:00 +0100, Matt Sealey wrote: > 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.. PVR wouldn't be very useful... What if you have altivec disabled ? Also that would mean your gdb has to know about all new processors... Ben.