Re: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump

On Wed, 24 Oct 2007 18:37:35 +0200 Bernhard Walle <[email protected]> wrote:

> This patch uses the BOOTMEM_EXCLUSIVE, introduced in the previous patch,
> to avoid conflicts while reserving the memory for the kdump carpture kernel
> (crashkernel=).
> 
> 
> Signed-off-by: Bernhard Walle <[email protected]>
> 
> ---
>  arch/sh/kernel/setup.c     |   29 ++++++++++++++++++-----------
>  arch/x86/kernel/setup_32.c |   28 ++++++++++++++++++----------
>  arch/x86/kernel/setup_64.c |   35 +++++++++++++++++++++--------------

ia64 and powerpc support crash dump too?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
    • From: Paul Mundt <[email protected]>

• References:
  • [patch 0/2] Add flags to reserve_bootmem()
    • From: Bernhard Walle <[email protected]>
  • [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
    • From: Bernhard Walle <[email protected]>

• Prev by Date: Re: Is gcc thread-unsafe?
• Next by Date: Re: How to debug complete kernel lock-ups
• Previous by thread: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
• Next by thread: Re: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]