From: Mohan Kumar M <mohan@in.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: ppcdev <linuxppc-dev@ozlabs.org>, kexec@lists.infradead.org
Subject: Re: [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
Date: Thu, 09 Oct 2008 22:04:16 +0530 [thread overview]
Message-ID: <48EE3288.7080105@in.ibm.com> (raw)
In-Reply-To: <18669.38794.476429.103254@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
>
> Hmmm. Is there any reason to continue to support non-relocatable
> 64-bit kernels being kdump kernels? In other words, for 64-bit,
> couldn't we make CONFIG_CRASH_DUMP depend on CONFIG_RELOCATABLE?
We wanted to support legacy kdump feature on 64 bit kernels for some
time. But if nobody needs the legacy kdump, we can make kdump depend on
relocatable
Regards,
Mohan.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Mohan Kumar M <mohan@in.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: ppcdev <linuxppc-dev@ozlabs.org>, kexec@lists.infradead.org
Subject: Re: [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
Date: Thu, 09 Oct 2008 22:04:16 +0530 [thread overview]
Message-ID: <48EE3288.7080105@in.ibm.com> (raw)
In-Reply-To: <18669.38794.476429.103254@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
>
> Hmmm. Is there any reason to continue to support non-relocatable
> 64-bit kernels being kdump kernels? In other words, for 64-bit,
> couldn't we make CONFIG_CRASH_DUMP depend on CONFIG_RELOCATABLE?
We wanted to support legacy kdump feature on 64 bit kernels for some
time. But if nobody needs the legacy kdump, we can make kdump depend on
relocatable
Regards,
Mohan.
next prev parent reply other threads:[~2008-10-09 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 18:25 [PATCH] Fix kdump kernel hang issue with relocatable kernel patches Mohan Kumar M
2008-10-01 18:25 ` Mohan Kumar M
2008-10-09 5:32 ` Paul Mackerras
2008-10-09 5:32 ` Paul Mackerras
2008-10-09 16:34 ` Mohan Kumar M [this message]
2008-10-09 16:34 ` Mohan Kumar M
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=48EE3288.7080105@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.