All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bernhard Walle <bwalle@suse.de>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linuxsh-dev@lists.sourceforge.net
Subject: Re: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
Date: Thu, 25 Oct 2007 13:14:54 +0900	[thread overview]
Message-ID: <20071025041454.GB25376@linux-sh.org> (raw)
In-Reply-To: <20071024210533.b919dba3.akpm@linux-foundation.org>

On Wed, Oct 24, 2007 at 09:05:33PM -0700, Andrew Morton wrote:
> On Wed, 24 Oct 2007 18:37:35 +0200 Bernhard Walle <bwalle@suse.de> 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 <bwalle@suse.de>
> > 
> > ---
> >  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 <lethal@linux-sh.org>

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

WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bernhard Walle <bwalle@suse.de>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linuxsh-dev@lists.sourceforge.net
Subject: Re: [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump
Date: Thu, 25 Oct 2007 13:14:54 +0900	[thread overview]
Message-ID: <20071025041454.GB25376@linux-sh.org> (raw)
In-Reply-To: <20071024210533.b919dba3.akpm@linux-foundation.org>

On Wed, Oct 24, 2007 at 09:05:33PM -0700, Andrew Morton wrote:
> On Wed, 24 Oct 2007 18:37:35 +0200 Bernhard Walle <bwalle@suse.de> 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 <bwalle@suse.de>
> > 
> > ---
> >  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 <lethal@linux-sh.org>

  reply	other threads:[~2007-10-25  4:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:37 [patch 0/2] Add flags to reserve_bootmem() Bernhard Walle
2007-10-24 16:37 ` [patch 1/2] Introduce flags for reserve_bootmem() Bernhard Walle
2007-10-24 16:37 ` [patch 2/2] Use BOOTMEM_EXCLUSIVE for kdump Bernhard Walle
2007-10-24 16:37   ` Bernhard Walle
2007-10-25  4:05   ` Andrew Morton
2007-10-25  4:05     ` Andrew Morton
2007-10-25  4:14     ` Paul Mundt [this message]
2007-10-25  4:14       ` Paul Mundt

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=20071025041454.GB25376@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxsh-dev@lists.sourceforge.net \
    /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.