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

On Wed, Oct 24, 2007 at 09:05:33PM -0700, Andrew Morton wrote:
> 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?
> 
Not via a reserved bootmem area at least, which is what these patches
touch.

Acked-by: Paul Mundt <[email protected]>
-
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/

---

• 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]>
  • Re: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
    • From: Andrew Morton <[email protected]>

• Prev by Date: QUESTION: How to fix race between .suspend routine and watchdog timer
• Next by Date: Re: [PATCH 4/5] Add lock_page_killable
• Previous by thread: Re: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
• Next by thread: [patch 1/2] Introduce flags for reserve_bootmem()
• 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]