| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20110407131250.GA1571@aepfle.de> Date: Thu, 7 Apr 2011 15:12:50 +0200 From: Olaf Hering <olaf@...fle.de> To: Américo Wang <xiyou.wangcong@...il.com> Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org Subject: Re: dynamic oldmem in kdump kernel On Thu, Apr 07, Américo Wang wrote: > On Thu, Apr 7, 2011 at 5:56 PM, Olaf Hering <olaf@...fle.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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists