All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bwalle@suse.de, kexec@lists.infradead.org
Subject: Re: [PATCH] Make extended crashkernel= syntax less confusing
Date: Thu, 01 May 2008 09:16:30 +1000	[thread overview]
Message-ID: <1209597390.7592.4.camel@localhost> (raw)
In-Reply-To: <20080430112915.f56d8815.akpm@linux-foundation.org>


[-- Attachment #1.1: Type: text/plain, Size: 2055 bytes --]

On Wed, 2008-04-30 at 11:29 -0700, Andrew Morton wrote:
> On Wed, 30 Apr 2008 11:36:27 +1000 (EST)
> Michael Ellerman <michael@ellerman.id.au> wrote:
> 
> > The extended crashkernel syntax is a little confusing in the
> > way it handles ranges. eg:
> > 
> >  crashkernel=512M-2G:64M,2G-:128M
> > 
> > Means if the machine has between 512M and 2G of memory the
> > crash region should be 64M, and if the machine has 2G of
> > memory the region should be 64M. Only if the machine has
> > more than 2G memory will 128M be allocated.
> > 
> > Although that semantic is correct, it is somewhat baffling.
> > Instead I propose that the end of the range means the first
> > address past the end of the range, ie: 512M up to but not
> > including 2G.
> > 
> > Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> > Acked-by: Bernhard Walle <bwalle@suse.de>
> > ---
> > 
> >  kernel/kexec.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/kernel/kexec.c b/kernel/kexec.c
> > index 6782dce..0ab5e33 100644
> > --- a/kernel/kexec.c
> > +++ b/kernel/kexec.c
> > @@ -1217,7 +1217,7 @@ static int __init parse_crashkernel_mem(char 			*cmdline,
> >  		}
> >  
> >  		/* match ? */
> > -		if (system_ram >= start && system_ram <= end) {
> > +		if (system_ram >= start && system_ram < end) {
> >  			*crash_size = size;
> >  			break;
> >  		}
> 
> I'm a bit surprised to see the code being updated but not the
> documentation.  Were they out of sync before or are they out of sync after
> this patch or were they always in sync or what?

Well I think my patch makes the code match the documentation, but it
depends on how you interpret "between xM and yM".

Bernhard's patch to make it explicit is a good idea though.

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 #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

      parent reply	other threads:[~2008-04-30 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  1:36 [PATCH] Make extended crashkernel= syntax less confusing Michael Ellerman
2008-04-30 18:29 ` Andrew Morton
2008-04-30 21:57   ` Bernhard Walle
2008-05-01  0:16     ` Simon Horman
2008-04-30 23:16   ` Michael Ellerman [this message]

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=1209597390.7592.4.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=akpm@linux-foundation.org \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.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.