From: James Bottomley <James.Bottomley@steeleye.com>
To: Keith Owens <kaos@sgi.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC] crash_stop: crash_stop_i386_handler
Date: Fri, 13 Oct 2006 08:55:35 -0500 [thread overview]
Message-ID: <1160747735.3433.3.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <27440.1160745940@ocs3.ocs.com.au>
On Fri, 2006-10-13 at 23:25 +1000, Keith Owens wrote:
> Note 2: This patch does not cover i386 voyager. I do not understand
> the voyager interrupt mechanism well enough to define its
> interrupt handlers (hint, hint).
Voyager actually doesn't need a software based crash dump at all.
The system itself has a type of GSP that runs SUS (sort of a bios)
continuously. SUS will dump a complete memory and state image to a
nominated dump slice (usually swap) if the OS becomes unresponsive or
requests it. So all I really have to do is come up with a user space
tool that converts from this raw image format to your crash tool format.
James
next prev parent reply other threads:[~2006-10-13 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 13:23 [RFC] Common API for bring the system to a crash_stop state Keith Owens
2006-10-13 13:24 ` [RFC] crash_stop: crash_stop_headers Keith Owens
2006-10-13 13:25 ` [RFC] crash_stop: crash_stop_i386_handler Keith Owens
2006-10-13 13:55 ` James Bottomley [this message]
2006-10-13 14:00 ` Keith Owens
2006-10-13 13:26 ` [RFC] crash_stop: crash_stop_i386 Keith Owens
2006-10-13 13:27 ` [RFC] crash_stop: crash_stop_common Keith Owens
2006-10-13 13:28 ` [RFC] crash_stop: crash_stop_common_Kconfig Keith Owens
2006-10-13 13:28 ` [RFC] crash_stop: crash_stop_demo Keith Owens
2006-10-13 13:45 ` [RFC] Common API for bring the system to a crash_stop state Keith Owens
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=1160747735.3433.3.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=kaos@sgi.com \
--cc=linux-arch@vger.kernel.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.