From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48962) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgEsU-0001yN-Su for qemu-devel@nongnu.org; Tue, 12 Nov 2013 09:23:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VgEsO-0001u5-PF for qemu-devel@nongnu.org; Tue, 12 Nov 2013 09:23:38 -0500 Received: from mx3-phx2.redhat.com ([209.132.183.24]:42734) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgEsO-0001tk-Gg for qemu-devel@nongnu.org; Tue, 12 Nov 2013 09:23:32 -0500 Date: Tue, 12 Nov 2013 09:23:29 -0500 (EST) From: Dave Anderson Message-ID: <341971871.21068752.1384266208992.JavaMail.root@redhat.com> In-Reply-To: <52813228.5090705@redhat.com> References: <528029C1.6040800@redhat.com> <52813228.5090705@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] dump-guest-memory enhancement. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Phi Debian , QEMU Developers ----- Original Message ----- > I haven't been there at the original creation of this functionality, but > I tend to agree with you. For analyzing the vmcore with gdb or crash, > the alignment doesn't seem to be important, so it was probably ignored. With respect to the crash utility, the p_align field is actually used to differentiate kdump ELF vmcores from the old netdump ELF vmcores. There are a couple subtle differences between the old netdump ELF vmcores and kdump ELF vmcores. Netdump ELF vmcores set the the p_align field to the architecture page size, whereas kdump ELF vmcores have always had a p_align field of zero. Ideally these virsh-dump vmcores would continue to be essentially kdump clones. But if it's changed, then there will need to be an update to the crash utility to work around it. Dave