From: Olaf Hering <olaf@aepfle.de>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: dynamic oldmem in kdump kernel
Date: Thu, 7 Apr 2011 15:12:50 +0200 [thread overview]
Message-ID: <20110407131250.GA1571@aepfle.de> (raw)
In-Reply-To: <BANLkTimXRcKyWdUxS2TRzibcSUdCfObH3g@mail.gmail.com>
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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Olaf Hering <olaf@aepfle.de>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: dynamic oldmem in kdump kernel
Date: Thu, 7 Apr 2011 15:12:50 +0200 [thread overview]
Message-ID: <20110407131250.GA1571@aepfle.de> (raw)
In-Reply-To: <BANLkTimXRcKyWdUxS2TRzibcSUdCfObH3g@mail.gmail.com>
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
next prev parent reply other threads:[~2011-04-07 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 9:56 dynamic oldmem in kdump kernel Olaf Hering
2011-04-07 9:56 ` Olaf Hering
2011-04-07 10:23 ` Américo Wang
2011-04-07 10:23 ` Américo Wang
2011-04-07 13:12 ` Olaf Hering [this message]
2011-04-07 13:12 ` Olaf Hering
2011-04-08 10:49 ` Américo Wang
2011-04-08 10:49 ` Américo Wang
2011-05-02 10:22 ` Olaf Hering
2011-05-02 10:22 ` Olaf Hering
2011-05-03 19:08 ` [PATCH] add hook to read_from_oldmem() to check for non-ram pages Olaf Hering
2011-05-03 19:08 ` Olaf Hering
2011-05-05 21:25 ` Andrew Morton
2011-05-05 21:25 ` Andrew Morton
2011-05-06 10:55 ` Olaf Hering
2011-05-06 10:55 ` Olaf Hering
2011-05-06 19:30 ` Andrew Morton
2011-05-06 19:30 ` Andrew Morton
2011-05-06 19:39 ` Olaf Hering
2011-05-06 19:39 ` Olaf Hering
2011-05-06 19:55 ` Andrew Morton
2011-05-06 19:55 ` Andrew Morton
2011-05-06 13:20 ` [PATCH v2] " Olaf Hering
2011-05-06 13:20 ` Olaf Hering
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=20110407131250.GA1571@aepfle.de \
--to=olaf@aepfle.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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.