Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755033Ab3EXP3i (ORCPT ); Fri, 24 May 2013 11:29:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32078 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752105Ab3EXP3h (ORCPT ); Fri, 24 May 2013 11:29:37 -0400 Date: Fri, 24 May 2013 11:28:49 -0400 From: Vivek Goyal To: Michael Holzheu Cc: HATAYAMA Daisuke , Jan Willeke , Martin Schwidefsky , Heiko Carstens , linux-kernel@vger.kernel.org, kexec@lists.infradead.org, Andrew Morton , "Eric W. Biederman" Subject: Re: [PATCH 0/2] kdump/mmap: Fix mmap of /proc/vmcore for s390 Message-ID: <20130524152849.GF18218@redhat.com> References: <1369400889-11064-1-git-send-email-holzheu@linux.vnet.ibm.com> <20130524143644.GD18218@redhat.com> <20130524170626.2ac06efe@holzheu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524170626.2ac06efe@holzheu> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2492 Lines: 62 On Fri, May 24, 2013 at 05:06:26PM +0200, Michael Holzheu wrote: > Hello Vivek, > > On Fri, 24 May 2013 10:36:44 -0400 > Vivek Goyal wrote: > > [snip] > > > Sorry, I don't understand the problem. If we swapped low memory and > > crash reserved memory, that should have been taken care by prepared > > ELF headers so that we map the right pfns. In x86 we swap 640K of low > > memory with 640K of memory in reserved and we take care of this by > > preparing elf headers accordingly. > > > > So why s390 can't do the same thing? > > I am not sure if I understand this. Currently we create the ELF > header in a way that we have virtual=real. In the copy_oldmem_page() we > do the swap so that for the /proc/vmcore code it looks like contiguous > non-swapped memory. > > One reason why I thought this was necessary was that /dev/oldmem > also uses the function and it should provide linear memory access like > it is on the live system with /dev/mem. > > Is that implementation incorrect? [ CC Andrew. Keep him in loop for all kernel kdump patches as all kdump patches are routed through him ]. [ CC Eric Biederman ] Looking at the code, looks like /dev/oldmem is broken. It does not know anything about swap of any of the memory areas and it will simply return the contents of page frame asked. And this has been like this since the beginning. I have always questioned the utility of /dev/oldmem. Atleast I am not aware of any tool making use of it. If we want to fix it, then somebow all the swapped memory region info needs to be communicated to second kernel so that read_oldmem() can do the mapping correctly and we really don't have any mechanism for that. (I am assuming that in s390 you must have hardcoded the regions of memory which are always swapped). As /proc/vmcore is the most used and useful interface, I prefer that we swap memory and put that info in elf headers. For /dev/oldme, I don't mind if we leave it as it is. If somebody really cares, then I guess we need to write a new command line option which /dev/mem can parse and which tells it about swaps so that /dev/oldmem can map things correctly. (This is better than hardcoding things). Eric, do you have any thoughts on this. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/