public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 3/3] IA64: verify the base address of crashkernel
Date: Wed, 07 Mar 2007 00:50:03 +0000	[thread overview]
Message-ID: <20070307005002.GD17090@verge.net.au> (raw)
In-Reply-To: <20070306073756.245032985@tabatha.lab.ultramonkey.org>

On Tue, Mar 06, 2007 at 04:23:37PM +0800, Zou, Nanhai wrote:
> 
> Hi Horms,
> 	I feel this is over-designed.
>      I think to specify crash kernel base address in command line is only useful for debug, on platform like SN this feature is totally unusable.At the most of time, user should let kernel to decide where to reserve crashdump region.
>     If a user wants to put crash kernel in command line, he should know what he is doing.

Hi Nanhai,

while I do agree that perhaps these checks are a little verbose I don't
agree that they are uneccessary. Specifying the base address is entirely
sane on some platforms (e.g. Tiger 2). And more to the point, it is the
only method available on some architectures, and thus its seems
reasonable to expect that it might work sanley on ia64. It seems to me
that it is a good idea to have some checks in place, in line with the
checks performed when the base address is automatically determinted to
make the behaviour (more) consistent. 

Ideally it would be good if there were not two code-paths relating
to base address selection - auto and manual. Or more to the point, if
they could share the same checks. But at this point I can't see a way to
make the code do that.

I guess in the end it comes down to how easy you want it to be for users
mistakes to be caught. I think that currently kexec/kdump is quite
fragile and its easy to end up with a setup that doesn't work. I think
that changes like this one are one small step towards making a more
robust system. Ditto for the change regarding loging success or failure
of inserting the crashkernel region.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


  parent reply	other threads:[~2007-03-07  0:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06  7:28 [patch 3/3] IA64: verify the base address of crashkernel Horms
2007-03-06  8:23 ` Zou, Nanhai
2007-03-06 17:08 ` Aron Griffis
2007-03-07  0:42 ` Horms
2007-03-07  0:50 ` Horms [this message]
2007-03-07  0:57 ` Horms
2007-03-07  2:15 ` Zou, Nanhai
2007-03-07  3:46 ` Horms
2007-03-07  4:50 ` Zou, Nanhai
2007-03-07  7:55 ` Horms
2007-03-07  9:06 ` Zou, Nanhai
2007-03-07  9:49 ` Horms

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=20070307005002.GD17090@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox