From: "André Detsch" <adetsch@br.ibm.com>
To: michael@ellerman.id.au
Cc: Arnd Bergmann <arnd.bergmann@de.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
Luke Browning <LukeBrowning@us.ibm.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Lucio Jose Herculano Correia <luciojhc@br.ibm.com>,
cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] [patch 4/5] cell: saving spus information for kexec crash
Date: Wed, 20 Jun 2007 15:52:38 -0300 [thread overview]
Message-ID: <46797776.3070202@br.ibm.com> (raw)
In-Reply-To: <1182211119.23887.3.camel@concordia.ozlabs.ibm.com>
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 <adetsch@br.ibm.com>
>> 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 <luciojhc@br.ibm.com>
>> Signed-off-by: Andre Detsch <adetsch@br.ibm.com>
>> Signed-off-by: Arnd Bergmann <arnd.bergmann@de.ibm.com>
>
>
> 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
next prev parent reply other threads:[~2007-06-20 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 22:42 [patch 0/5] cell patches for 2.6.23 Arnd Bergmann
2007-06-18 22:42 ` [patch 1/5] Enable SPU switch notification to detect currently active SPU tasks Arnd Bergmann
2007-06-18 22:42 ` [patch 2/5] Add support to OProfile for profiling Cell/B.E. SPUs Arnd Bergmann
2007-06-20 2:32 ` [Cbe-oss-dev] " mita
2007-06-20 9:35 ` Arnd Bergmann
2007-06-18 22:42 ` [patch 3/5] cell: updated driver for DDR2 memory on AXON Arnd Bergmann
[not found] ` <20070619154812.GA20347@ps3linux.grid.fixstars.com>
2007-06-19 23:03 ` [Cbe-oss-dev] " Arnd Bergmann
2007-06-18 22:42 ` [patch 4/5] cell: saving spus information for kexec crash Arnd Bergmann
2007-06-18 23:58 ` [Cbe-oss-dev] " Michael Ellerman
2007-06-20 18:52 ` André Detsch [this message]
2007-06-18 22:42 ` [patch 5/5] Update cell_defconfig Arnd Bergmann
2007-06-18 23:01 ` [Cbe-oss-dev] [patch 0/5] cell patches for 2.6.23 Arnd Bergmann
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=46797776.3070202@br.ibm.com \
--to=adetsch@br.ibm.com \
--cc=LukeBrowning@us.ibm.com \
--cc=arnd.bergmann@de.ibm.com \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=luciojhc@br.ibm.com \
--cc=michael@ellerman.id.au \
/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).