Le 07/03/2014 à 05:38, Nikita Yushchenko a écrit :
On Thu, 2014-03-06 at 18:24 +0400, Nikita Yushchenko wrote:
When preparing dump-capturing kernel, kexec userspace tool needs to
know actual amount of memory used by the running kernel. This may
differ from extire available DRAM for a couple
When preparing dump-capturing kernel, kexec userspace tool needs to know
actual amount of memory used by the running kernel. This may differ from
extire available DRAM for a couple of reasons. To address this issue,
kdump kernel support code injects several attributes into device tree that
are
On Thu, 2014-03-06 at 18:24 +0400, Nikita Yushchenko wrote:
When preparing dump-capturing kernel, kexec userspace tool needs to know
actual amount of memory used by the running kernel. This may differ from
extire available DRAM for a couple of reasons. To address this issue,
kdump kernel
On Thu, 2014-03-06 at 18:24 +0400, Nikita Yushchenko wrote:
When preparing dump-capturing kernel, kexec userspace tool needs to
know actual amount of memory used by the running kernel. This may
differ from extire available DRAM for a couple of reasons. To address
this issue, kdump kernel
