lkml.org 
[lkml]   [2014]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[RFC PATCH 0/2] transfer sparse memory related values
Date
Now different platforms may have different SECTION_SIZE_BITS and
MAX_PHYSMEM_BITS. But linux passes nothing related to the
vmcore.

User space tools such as makedumpfile needs these to deal with
the vmcore. So we must define these when compiling. So if we
deal with aother vmcore. We may need to recompile the tools.

These patch series make kernel pass related infomation to
the user space tools, via vmcore. And makedumpfile can
get these when parsing vmcore. So the makdumpfile becomes
more compatible to vmcore with different section size.


Liu Hua (1):
kdump: add sparse memory related values to vmcore
makedumpfile: get additional information from vmcore

kernel/kexec.c | 3 +++
makedumpfile.c | 17 +++++++++++++++++
makedumpfile.h | 2 ++
3 files changed, 22 insertions(+)

--
1.9.0



\
 
 \ /
  Last update: 2014-05-07 17:21    [W:0.052 / U:0.376 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site