From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <46797776.3070202@br.ibm.com> Date: Wed, 20 Jun 2007 15:52:38 -0300 From: =?ISO-8859-1?Q?Andr=E9_Detsch?= MIME-Version: 1.0 To: michael@ellerman.id.au Subject: Re: [Cbe-oss-dev] [patch 4/5] cell: saving spus information for kexec crash References: <20070618224247.972139855@arndb.de> <20070618224923.498962312@arndb.de> <1182211119.23887.3.camel@concordia.ozlabs.ibm.com> In-Reply-To: <1182211119.23887.3.camel@concordia.ozlabs.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Arnd Bergmann , Arnd Bergmann , Luke Browning , linuxppc-dev list , Lucio Jose Herculano Correia , cbe-oss-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Michael Ellerman wrote: > On Tue, 2007-06-19 at 00:42 +0200, Arnd Bergmann wrote: >> plain text document attachment (cell-spus-info-kexec-crash-1.diff) >> From: Andre Detsch >> 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 from xmon. >> >> Signed-off-by: Lucio Jose Herculano Correia >> Signed-off-by: Andre Detsch >> Signed-off-by: Arnd Bergmann > > > I'd like to have this patch share the emergency stopping logic with the > xmon code, I'll try and get a patch done in the next few days. > Hi Michael, What aspect of the patch do you think would benefit from sharing logic with xmon? The structures (struct crash_spu + crash_register_spus function) or the stop spus logic itself (crash_kexec_stop_spus)? Or both? My first approach was actually to use the same structure and code as xmon (as you might remember from an private email I've sent before posting the patch). However, talking with Luke, we decided to keep xmon and crash data independent from each other, since he was interested on eventually allowing xmon to be run before the second kernel gets loaded. So, having a separate structure for crash info would allow us to save the exact state when the crash occurred, no matter of what the user did while running xmon. Best regards, -- Andre Detsch