Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756213Ab3EYNNg (ORCPT ); Sat, 25 May 2013 09:13:36 -0400 Received: from e06smtp15.uk.ibm.com ([195.75.94.111]:50850 "EHLO e06smtp15.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755217Ab3EYNNe (ORCPT ); Sat, 25 May 2013 09:13:34 -0400 Date: Sat, 25 May 2013 15:13:24 +0200 From: Michael Holzheu To: Vivek Goyal 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: <20130525151324.637d6b70@holzheu> In-Reply-To: <20130524170507.GG18218@redhat.com> References: <1369400889-11064-1-git-send-email-holzheu@linux.vnet.ibm.com> <20130524143644.GD18218@redhat.com> <20130524170626.2ac06efe@holzheu> <20130524152849.GF18218@redhat.com> <20130524184653.52d75b5f@holzheu> <20130524170507.GG18218@redhat.com> Organization: IBM X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13052513-0342-0000-0000-00000521EF51 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1908 Lines: 53 On Fri, 24 May 2013 13:05:07 -0400 Vivek Goyal wrote: > On Fri, May 24, 2013 at 06:46:53PM +0200, Michael Holzheu wrote: > > On Fri, 24 May 2013 11:28:49 -0400 > > Vivek Goyal wrote: > > > > > On Fri, May 24, 2013 at 05:06:26PM +0200, Michael Holzheu wrote: > > > > [snip] > > > > > 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). > > > > Besides of the potential /dev/oldmem issue, I still do not > > understand the option of doing the swap in the elf header. Looks > > like I missed here a fundamental design point of kdump :( > > > > Is that done by specifying different virtual and physical addresses > > in the ELF header? > > Nope. We keep the virtual to physical address mapping same. We just > modify the p_offset in PT_LOAD elf header to represent where actually > the memory is present physically. And when /proc/vmcore reads the > data, it reads it from p_offset. > > IOW, p_offset and p_paddr will be different for swapped memory but > should be same for memory which has not been swapped. Hello Vivek, Ok, now I got it :) It worked for me by specifying a PT_LOAD with: phdr->p_offset = OLDMEM_BASE; phdr->p_vaddr = phdr->p_paddr = 0; phdr->p_filesz = phdr->p_memsz = OLDMEM_SIZE; Best Regards, Michael -- 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/