Date: Tue, 22 Jun 2010 09:31:27 +0530
From: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Message-ID: <20100622040127.GA27051@in.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Qemu-devel] [patch 0/3] QEMU-C-F: Userspace tool to filter guest
 OS memory from qemu coredump
To: qemu-devel@nongnu.org
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>, Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>, Maneesh Soni <maneesh@in.ibm.com>, Michael Mueller <mimu@de.ibm.com>, Reinhard Buendgen <BEUNDGEN@de.ibm.com>

Hi All,

Please find the patch series that implements qemu-core-filter, a userspace
tool to filter out guest OS memory from qemu coredump.

The qemu-core-filter tool is a post-processing tool works offline on qemu
coredumps. When  qemu[-kvm]  application crashes, it generates a huge coredump
file that contains guest OS memory. This tool helps to reduce the size of
core file (generated by qemu crash) by removing guest OS memory from original
core file.

The tool requires qemu[-kvm] debug information to be able to identify and
exclude guest OS memory regions from core file. The reason is debuginfo
contains a symbol table that keeps the variable name to address mapping's.
The qemu-core-filter tool uses this symbol table to locate a global variable
'ram_blocks' that has the Guest OS memory region mapping's.

When we ran it against a a qemu coredump of 570Mb size, it created ouput
coredump file of size 42M.

Please review the patches and let me know your comments.

Thanks,
-Mahesh.
-- 
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>