All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Mohan Kumar M <mohan@in.ibm.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>,
	paulus@samba.org, kexec@lists.infradead.org
Subject: Re: [PATCH] Remove legacy kdump kernel build support
Date: Tue, 30 Sep 2008 21:25:40 +0400	[thread overview]
Message-ID: <20080930172540.GA21378@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20080930124828.GA1945@in.ibm.com>

On Tue, Sep 30, 2008 at 06:18:28PM +0530, Mohan Kumar M wrote:
> Remove legacy kdump kernel build support
> 
> This patch removes legacy kdump kernel build support(i.e compiling  a
> kdump kernel at a fixed hardcoded address 32MB). With the relocatable
> kernel support its now possible to use the regular kernel binary for
> capturing the dump also. Relocatable kdump kernel does not require
> trampoline code for exception handlers. It removes kdump.h as most of the
> macros defined in kdump.h are not used any more. Also the relocatable
> kdump kernel allows us to load kdump kernel any where as specified by
> crashkernel parameter instead of hardcoded address 32MB.

Can we leave the legacy support for a while? On PPC32 we don't have
the relocatable kernel support, but we have kdump patches floating
around[1], and they use the `hard-coded values' approach, so far.

I'm not sure if anybody is currently working on a PPC32 kernel
relocation support.. but for sure it will take some time to implement.

Thanks,

[1] http://ozlabs.org/pipermail/linuxppc-dev/2008-August/061161.html

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Mohan Kumar M <mohan@in.ibm.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>,
	paulus@samba.org, kexec@lists.infradead.org
Subject: Re: [PATCH] Remove legacy kdump kernel build support
Date: Tue, 30 Sep 2008 21:25:40 +0400	[thread overview]
Message-ID: <20080930172540.GA21378@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20080930124828.GA1945@in.ibm.com>

On Tue, Sep 30, 2008 at 06:18:28PM +0530, Mohan Kumar M wrote:
> Remove legacy kdump kernel build support
> 
> This patch removes legacy kdump kernel build support(i.e compiling  a
> kdump kernel at a fixed hardcoded address 32MB). With the relocatable
> kernel support its now possible to use the regular kernel binary for
> capturing the dump also. Relocatable kdump kernel does not require
> trampoline code for exception handlers. It removes kdump.h as most of the
> macros defined in kdump.h are not used any more. Also the relocatable
> kdump kernel allows us to load kdump kernel any where as specified by
> crashkernel parameter instead of hardcoded address 32MB.

Can we leave the legacy support for a while? On PPC32 we don't have
the relocatable kernel support, but we have kdump patches floating
around[1], and they use the `hard-coded values' approach, so far.

I'm not sure if anybody is currently working on a PPC32 kernel
relocation support.. but for sure it will take some time to implement.

Thanks,

[1] http://ozlabs.org/pipermail/linuxppc-dev/2008-August/061161.html

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  parent reply	other threads:[~2008-09-30 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 12:48 [PATCH] Remove legacy kdump kernel build support Mohan Kumar M
2008-09-30 12:48 ` Mohan Kumar M
2008-09-30 12:53 ` [PATCH 2/2] Support for relocatable kdump kernel Mohan Kumar M
2008-09-30 12:53   ` Mohan Kumar M
2008-09-30 17:25 ` Anton Vorontsov [this message]
2008-09-30 17:25   ` [PATCH] Remove legacy kdump kernel build support Anton Vorontsov
2008-10-01 18:36   ` Mohan Kumar M
2008-10-01 18:36     ` 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=20080930172540.GA21378@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mohan@in.ibm.com \
    --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.