From: Ralf Baechle <ralf@linux-mips.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: kexec on SMP mips64?
Date: Fri, 1 Feb 2008 09:32:09 +0000 [thread overview]
Message-ID: <20080201093209.GA18195@linux-mips.org> (raw)
In-Reply-To: <47A21286.3020009@nortel.com>
On Thu, Jan 31, 2008 at 12:25:10PM -0600, Chris Friesen wrote:
> We're starting work on an embedded highly-available product using dual
> Octeon cpus, and I'm looking into the possibility of using kexec/kdump as a
> "flight recorder" to dump fault information to a persistant storage
> location.
>
> I saw the patch adding initial support for kexec, but I was curious about
> the current status. Is anyone using kexec for mips64 SMP systems? Is it
> known to be broken? I'm just trying to get a feel for how much work might
> be involved.
I would classify the code as untested and suspect.
Ralf
next prev parent reply other threads:[~2008-02-01 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 18:25 kexec on SMP mips64? Chris Friesen
2008-02-01 9:32 ` Ralf Baechle [this message]
2008-02-01 12:21 ` Nicolas Schichan
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=20080201093209.GA18195@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=cfriesen@nortel.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox