Date: Thu, 7 Apr 2011 15:12:50 +0200
From: Olaf Hering <olaf@aepfle.de>
To: =?utf-8?Q?Am=C3=A9rico?= Wang <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: dynamic oldmem in kdump kernel
Message-ID: <20110407131250.GA1571@aepfle.de>
References: <20110407095646.GA30788@aepfle.de>
 <BANLkTimXRcKyWdUxS2TRzibcSUdCfObH3g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <BANLkTimXRcKyWdUxS2TRzibcSUdCfObH3g@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 968
Lines: 25

On Thu, Apr 07, Américo Wang wrote:

> On Thu, Apr 7, 2011 at 5:56 PM, Olaf Hering <olaf@aepfle.de> wrote:
> > Another issue, slightly related, is memory hotplug.
> > How is this currently handled for kdump?  Is there code which
> > automatically reconfigures the kdump kernel with the new memory ranges?
> >
> 
> No, the crashkernel memory is reserved during boot, and it is static after
> that (except you can shrink this memory via /sys).

I meant the overall amount of memory changed by memory hotplug events,
not the small memory range for the crash kernel itself.

> Kdump isn't aware of memory hotplug.

Ok.  Perhaps there are hotplug events where a helper script could run
something like 'rckdump restart'.

Olaf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/