From: Simon Horman <horms@verge.net.au>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
Kexec Mailing List <kexec@lists.infradead.org>,
Venkappa Mala <Venkappa.Mala@lntinfotech.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: Linux kernel crash dumps for ARM
Date: Wed, 6 Jan 2010 09:02:16 +1100 [thread overview]
Message-ID: <20100105220216.GA8630@verge.net.au> (raw)
In-Reply-To: <20100105190047.GD30868@flint.arm.linux.org.uk>
On Tue, Jan 05, 2010 at 07:00:47PM +0000, Russell King wrote:
> On Tue, Jan 05, 2010 at 08:16:28PM +1100, Simon Horman wrote:
> > To add to this, my understanding is that kexec support varies across
> > different ARM platforms - that is to say, it works on some and fails on
> > others. While this seems to be slowly improving, I'm also aware of any list
> > of what is supported and what isn't.
>
> I'm unaware of that; the only area of weakness with kexec that I'm
> aware of is when the ARMv7 processor support didn't implement the
> necessary code to bring the caches/mmu/tlbs into a safe state for
> software-reboot, which is also what's required by kexec.
Ok, I could well be mistaken and its just ARMv7 that has a few issues
at this time.
prev parent reply other threads:[~2010-01-05 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EB1A7C66AD0C92419BFFC785A947865A09EA8C9129@BLRINMSMBX01.bglrodc.lntinfotech.com>
2010-01-05 4:51 ` Linux kernel crash dumps for ARM Venkappa Mala
2010-01-05 5:20 ` Eric W. Biederman
2010-01-05 8:30 ` Bernhard Walle
2010-01-05 8:48 ` Paul Mundt
2010-01-05 9:16 ` Simon Horman
2010-01-05 19:00 ` Russell King
2010-01-05 22:02 ` Simon Horman [this message]
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=20100105220216.GA8630@verge.net.au \
--to=horms@verge.net.au \
--cc=Venkappa.Mala@lntinfotech.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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