From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Frank Fan <linuxppcstudy@gmail.com>, linuxppc-dev@ozlabs.org
Subject: Re: Need help to understand why kdump is for 64 bit PPC only
Date: Tue, 16 Dec 2008 07:33:04 +1100 [thread overview]
Message-ID: <1229373184.8332.3.camel@localhost> (raw)
In-Reply-To: <1228A590-B809-4EBB-BC6F-05525220656A@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Mon, 2008-12-15 at 13:35 -0600, Kumar Gala wrote:
> On Dec 15, 2008, at 12:58 PM, Frank Fan wrote:
>
> > Hello,
> >
> > I am working on a freescale MPC8572 CPU board and use 32 bit
> > Linux2.6.28. When I enable 64 bit, it shows "kdump" in "kernel
> > options". Otherwise, "kdump" is disabled.
> > Can someone give me some hint why kdump is for 64 bit PPC only?
>
> Probably because no one has implemented or tested it on ppc32/8572.
Pretty much, the 32-bit version of default_machine_kexec() is pretty
naïve, but you never know it might work.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-15 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 18:58 Need help to understand why kdump is for 64 bit PPC only Frank Fan
2008-12-15 19:35 ` Kumar Gala
2008-12-15 20:33 ` Michael Ellerman [this message]
2008-12-15 20:37 ` Josh Boyer
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=1229373184.8332.3.camel@localhost \
--to=michael@ellerman.id.au \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppcstudy@gmail.com \
/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.