From: Paul Mundt <lethal@linux-sh.org>
To: Venkappa Mala <Venkappa.Mala@lntinfotech.com>
Cc: "rmk+lkml@arm.linux.org.uk" <rmk+lkml@arm.linux.org.uk>,
Kexec Mailing List <kexec@lists.infradead.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux kernel crash dumps for ARM
Date: Tue, 5 Jan 2010 17:48:51 +0900 [thread overview]
Message-ID: <20100105084850.GA27860@linux-sh.org> (raw)
In-Reply-To: <m17hrx9lgo.fsf@fess.ebiederm.org>
On Mon, Jan 04, 2010 at 09:20:23PM -0800, Eric W. Biederman wrote:
> Venkappa Mala <Venkappa.Mala@lntinfotech.com> writes:
> >
> > 2) As per kexec supports, kexec-tool is required and this allows you to load directly
> > to a new kernel from the currently running one
> >
> > As from my side, i am not able to find arm implementation support in kexec-tools/crash sources.
> >
> > - is kexce-tool supported for ARM or not?
> >
It would be rather counterintuitive for the kernel to support kexec and
the necessary userspace components not to.
The MAINTAINERS file says:
KEXEC
M: Eric Biederman <ebiederm@xmission.com>
W: http://ftp.kernel.org/pub/linux/kernel/people/horms/kexec-tools/
L: kexec@lists.infradead.org
S: Maintained
F: include/linux/kexec.h
F: kernel/kexec.c
While the above URL redirects to gitweb, resulting in:
http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools.git;a=summary
A peripheral grep of the kexec-tools source results in:
$ git grep kdump | grep arm
kexec/arch/arm/kexec-arm.c: return 0; /* kdump is not supported on this platform (yet) */
So one could infer that kexec is supported on ARM whilst kdump is not. Adding
crashdump support requires both some kernel and kexec-tools glue, but is fairly
straightforward, just look at the other ports.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Venkappa Mala <Venkappa.Mala@lntinfotech.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"rmk+lkml@arm.linux.org.uk" <rmk+lkml@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: Linux kernel crash dumps for ARM
Date: Tue, 5 Jan 2010 17:48:51 +0900 [thread overview]
Message-ID: <20100105084850.GA27860@linux-sh.org> (raw)
In-Reply-To: <m17hrx9lgo.fsf@fess.ebiederm.org>
On Mon, Jan 04, 2010 at 09:20:23PM -0800, Eric W. Biederman wrote:
> Venkappa Mala <Venkappa.Mala@lntinfotech.com> writes:
> >
> > 2) As per kexec supports, kexec-tool is required and this allows you to load directly
> > to a new kernel from the currently running one
> >
> > As from my side, i am not able to find arm implementation support in kexec-tools/crash sources.
> >
> > - is kexce-tool supported for ARM or not?
> >
It would be rather counterintuitive for the kernel to support kexec and
the necessary userspace components not to.
The MAINTAINERS file says:
KEXEC
M: Eric Biederman <ebiederm@xmission.com>
W: http://ftp.kernel.org/pub/linux/kernel/people/horms/kexec-tools/
L: kexec@lists.infradead.org
S: Maintained
F: include/linux/kexec.h
F: kernel/kexec.c
While the above URL redirects to gitweb, resulting in:
http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools.git;a=summary
A peripheral grep of the kexec-tools source results in:
$ git grep kdump | grep arm
kexec/arch/arm/kexec-arm.c: return 0; /* kdump is not supported on this platform (yet) */
So one could infer that kexec is supported on ARM whilst kdump is not. Adding
crashdump support requires both some kernel and kexec-tools glue, but is fairly
straightforward, just look at the other ports.
next prev parent reply other threads:[~2010-01-05 8:49 UTC|newest]
Thread overview: 15+ 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 5:20 ` Eric W. Biederman
2010-01-05 8:30 ` Bernhard Walle
2010-01-05 8:30 ` Bernhard Walle
2010-01-05 8:48 ` Paul Mundt [this message]
2010-01-05 8:48 ` Paul Mundt
2010-01-05 9:16 ` Simon Horman
2010-01-05 9:16 ` Simon Horman
2010-01-05 19:00 ` Russell King
2010-01-05 19:00 ` Russell King
2010-01-05 22:02 ` Simon Horman
2010-01-05 22:02 ` Simon Horman
2010-01-20 20:39 Ofer Heifetz
-- strict thread matches above, loose matches on Subject: below --
2010-02-25 13:06 Ofer Heifetz
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=20100105084850.GA27860@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=Venkappa.Mala@lntinfotech.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.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 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.