All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: linux-arch@vger.kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 1/5] Extended crashkernel command line
Date: Tue, 11 Sep 2007 12:01:10 +0200	[thread overview]
Message-ID: <20070911100110.GB31038@suse.de> (raw)
In-Reply-To: <20070911061522.GD5053@in.ibm.com>

* Vivek Goyal <vgoyal@in.ibm.com> [2007-09-11 08:15]:
> 
> "offset" seems to be optional in the new syntax. What happens if user does
> not specify offset. I think crash_base will be set to zero and system will
> try to reserve x amount of memory start at zero? That would fail?

That's handled in the architecture specific code -- because it's
different on each architecture and the architecture specific code does
memory reservation. IA64 already can handle this case (on IA64,
specifying 0 is the same than leaving out the base address, and that's
why I wanted to keep that semantics). I think it doesn't also make
sense on i386/x86_64 to choose 0 as real base address, because the
value below 1 MB is special for booting ...

> I think we should add some intelligence for automatic selection of "offset"
> if user has not specified one. Automatically choose a chunk of free memory.
> This takes away the headache from user for selecting a right place. In fact
> one "offset" might not be valid for all the systems. I remember, somebody
> had reported that ACPI tables were mapped lower in the address space and
> reserving memory for kdump had failed.

I think you're right -- with the relocatable kernel it makes sense to
have the kernel to decide where to reservate that memory. But that's
beyond of the scope of that patch series -- however, I can come up
with a solution, after that patch has been finished.


Thanks,
   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 <bwalle@suse.de>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: linux-arch@vger.kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 1/5] Extended crashkernel command line
Date: Tue, 11 Sep 2007 12:01:10 +0200	[thread overview]
Message-ID: <20070911100110.GB31038@suse.de> (raw)
In-Reply-To: <20070911061522.GD5053@in.ibm.com>

* Vivek Goyal <vgoyal@in.ibm.com> [2007-09-11 08:15]:
> 
> "offset" seems to be optional in the new syntax. What happens if user does
> not specify offset. I think crash_base will be set to zero and system will
> try to reserve x amount of memory start at zero? That would fail?

That's handled in the architecture specific code -- because it's
different on each architecture and the architecture specific code does
memory reservation. IA64 already can handle this case (on IA64,
specifying 0 is the same than leaving out the base address, and that's
why I wanted to keep that semantics). I think it doesn't also make
sense on i386/x86_64 to choose 0 as real base address, because the
value below 1 MB is special for booting ...

> I think we should add some intelligence for automatic selection of "offset"
> if user has not specified one. Automatically choose a chunk of free memory.
> This takes away the headache from user for selecting a right place. In fact
> one "offset" might not be valid for all the systems. I remember, somebody
> had reported that ACPI tables were mapped lower in the address space and
> reserving memory for kdump had failed.

I think you're right -- with the relocatable kernel it makes sense to
have the kernel to decide where to reservate that memory. But that's
beyond of the scope of that patch series -- however, I can come up
with a solution, after that patch has been finished.


Thanks,
   Bernhard


  reply	other threads:[~2007-09-11 10:01 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09  8:39 [patch 0/5] Add extended crashkernel command line syntax Bernhard Walle
2007-09-09  8:39 ` Bernhard Walle
2007-09-09  8:39 ` [patch 1/5] Extended crashkernel command line Bernhard Walle
2007-09-09  8:39   ` Bernhard Walle
2007-09-11  6:15   ` Vivek Goyal
2007-09-11  6:15     ` Vivek Goyal
2007-09-11 10:01     ` Bernhard Walle [this message]
2007-09-11 10:01       ` Bernhard Walle
2007-09-12 11:23       ` Vivek Goyal
2007-09-12 11:23         ` Vivek Goyal
2007-09-12 11:35         ` Bernhard Walle
2007-09-12 11:35           ` Bernhard Walle
2007-09-11 13:14   ` Olaf Dabrunz
2007-09-11 13:14     ` Olaf Dabrunz
2007-09-11 15:32     ` Lombard, David N
2007-09-11 15:32       ` Lombard, David N
2007-09-11 17:21       ` Bernhard Walle
2007-09-11 17:21         ` Bernhard Walle
2007-09-09  8:39 ` [patch 2/5] Use extended crashkernel command line on i386 Bernhard Walle
2007-09-09  8:39   ` Bernhard Walle
2007-09-09  8:39 ` [patch 3/5] Use extended crashkernel command line on x86_64 Bernhard Walle
2007-09-09  8:39   ` Bernhard Walle
2007-09-09 17:27   ` [discuss] " Yinghai Lu
2007-09-09 17:27     ` Yinghai Lu
2007-09-09 18:52     ` Bernhard Walle
2007-09-09 18:52       ` Bernhard Walle
2007-09-09 21:06       ` Eric W. Biederman
2007-09-09 21:06         ` Eric W. Biederman
2007-09-11  5:14       ` Vivek Goyal
2007-09-11  5:14         ` Vivek Goyal
2007-09-11 10:01         ` Bernhard Walle
2007-09-11 10:01           ` Bernhard Walle
2007-09-09  8:39 ` [patch 4/5] Use extended crashkernel command line on IA64 Bernhard Walle
2007-09-09  8:39   ` Bernhard Walle
2007-09-09  8:39   ` Bernhard Walle
2007-09-09 13:01   ` Matthew Wilcox
2007-09-09 13:01     ` Matthew Wilcox
2007-09-09 13:01     ` Matthew Wilcox
2007-09-09 19:08     ` Bernhard Walle
2007-09-09 19:08       ` Bernhard Walle
2007-09-09 19:08       ` Bernhard Walle
2007-09-09  8:39 ` [patch 5/5] Add documentation for extended crashkernel syntax Bernhard Walle
2007-09-09  8:39   ` Bernhard Walle
2007-09-11  6:09 ` [patch 0/5] Add extended crashkernel command line syntax Vivek Goyal
2007-09-11  6:09   ` Vivek Goyal
2007-09-13 15:02   ` Bernhard Walle
2007-09-13 15:02     ` 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=20070911100110.GB31038@suse.de \
    --to=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@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.