All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bernhard@bwalle.de>
To: "M. Mohan Kumar" <mohan@in.ibm.com>
Cc: michael@ellerman.id.au, benh@kernel.crashing.org,
	kexec@lists.infradead.org, ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Reserve memory for kdump kernel within RMO region
Date: Fri, 27 Nov 2009 19:39:09 +0100	[thread overview]
Message-ID: <4B101CCD.8030909@bwalle.de> (raw)
In-Reply-To: <4B0FCC0C.8060103@in.ibm.com>

M. Mohan Kumar schrieb:
> Hi,
> 
> As of now the kdump kernel base is fixed to be 32MB. The intention of 
> this patch is to modify that behaviour (for relocatable kernels)
> 
> * Regular kernel size may exceed 32MB, in this case we can't have kdump 
> kernelbase as 32MB.
> 
> * crashkernel=auto also assumes that kdump kernelbase as 32MB, and it 
> may also fail in reserving memory for kdump kernel.

I'm not opposed to remove the 32MB restriction, but I would like to make
the behaviour independent of CONFIG_RELOCATABLE like it's on x86:

 - Use 32M if one specifies xxx@32M
 - Use preferrably 32M, but fall back to another address if one
   specifies xxx or xxx@0M.

I don't see any problem with that. But it would make behaviour equal
accross platforms.



Regards,
Bernhard



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

WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bernhard@bwalle.de>
To: "M. Mohan Kumar" <mohan@in.ibm.com>
Cc: kexec@lists.infradead.org, ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Reserve memory for kdump kernel within RMO region
Date: Fri, 27 Nov 2009 19:39:09 +0100	[thread overview]
Message-ID: <4B101CCD.8030909@bwalle.de> (raw)
In-Reply-To: <4B0FCC0C.8060103@in.ibm.com>

M. Mohan Kumar schrieb:
> Hi,
> 
> As of now the kdump kernel base is fixed to be 32MB. The intention of 
> this patch is to modify that behaviour (for relocatable kernels)
> 
> * Regular kernel size may exceed 32MB, in this case we can't have kdump 
> kernelbase as 32MB.
> 
> * crashkernel=auto also assumes that kdump kernelbase as 32MB, and it 
> may also fail in reserving memory for kdump kernel.

I'm not opposed to remove the 32MB restriction, but I would like to make
the behaviour independent of CONFIG_RELOCATABLE like it's on x86:

 - Use 32M if one specifies xxx@32M
 - Use preferrably 32M, but fall back to another address if one
   specifies xxx or xxx@0M.

I don't see any problem with that. But it would make behaviour equal
accross platforms.



Regards,
Bernhard

  reply	other threads:[~2009-11-27 18:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 13:17 [PATCH] Reserve memory for kdump kernel within RMO region M. Mohan Kumar
2009-11-25 13:17 ` M. Mohan Kumar
2009-11-25 18:52 ` Bernhard Walle
2009-11-25 18:52   ` Bernhard Walle
2009-11-26 11:12   ` M. Mohan Kumar
2009-11-26 11:12     ` M. Mohan Kumar
2009-11-26 19:26     ` Bernhard Walle
2009-11-26 19:26       ` Bernhard Walle
2009-11-27  8:35       ` M. Mohan Kumar
2009-11-27  8:35         ` M. Mohan Kumar
2009-11-27 11:51         ` Simon Horman
2009-11-27 11:51           ` Simon Horman
2009-11-27 12:54       ` M. Mohan Kumar
2009-11-27 12:54         ` M. Mohan Kumar
2009-11-27 18:39         ` Bernhard Walle [this message]
2009-11-27 18:39           ` Bernhard Walle

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=4B101CCD.8030909@bwalle.de \
    --to=bernhard@bwalle.de \
    --cc=benh@kernel.crashing.org \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=mohan@in.ibm.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.