linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
	Jan Willeke <willeke@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH 0/2] kdump/mmap: Fix mmap of /proc/vmcore for s390
Date: Fri, 24 May 2013 10:36:44 -0400	[thread overview]
Message-ID: <20130524143644.GD18218@redhat.com> (raw)
In-Reply-To: <1369400889-11064-1-git-send-email-holzheu@linux.vnet.ibm.com>

On Fri, May 24, 2013 at 03:08:07PM +0200, Michael Holzheu wrote:
> Hello Vivek and Hatayama,
> 
> Currently the /proc/vmcore mmap patches are not working on s390. The
> problem is that on s390 the kernel in not relocatable and therefore
> always runs in the lower memory area. Therefore for kdump on s390 we
> swap the lower memory area with the crashkernel area before starting
> the kdump kernel:
> 
> [0 - OLDMEM_SIZE] is mapped to [OLDMEM_BASE - OLDMEM_BASE + OLDMEM_SIZE]
> 
> To fix /proc/vmcore mmap memory below OLDMEMSIZE needs to be mapped
> with OLDMEM_BASE as offset. To achieve that, a new weak function
> arch_oldmem_remap_pfn_range() is introduced.
> 
> If you agree with our approach, could you integrate the two patches
> into the mmap patch series?

Hi Michael, 

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?

Thanks
Vivek

> 
> Best Regards,
> Michael
> 
> ---
> Jan Willeke (2):
>   kdump/mmap: Introduce arch_oldmem_remap_pfn_range()
>   s390/kdump/mmap: Implement arch_oldmem_remap_pfn_range() for s390
> 
>  arch/s390/kernel/crash_dump.c | 27 +++++++++++++++++++++++++++
>  fs/proc/vmcore.c              | 15 ++++++++++++++-
>  include/linux/crash_dump.h    |  5 +++++
>  3 files changed, 46 insertions(+), 1 deletion(-)
> 
> -- 
> 1.8.1.6

  parent reply	other threads:[~2013-05-24 14:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 13:08 [PATCH 0/2] kdump/mmap: Fix mmap of /proc/vmcore for s390 Michael Holzheu
2013-05-24 13:08 ` [PATCH 1/2] kdump/mmap: Introduce arch_oldmem_remap_pfn_range() Michael Holzheu
2013-05-24 13:08 ` [PATCH 2/2] s390/kdump/mmap: Implement arch_oldmem_remap_pfn_range() for s390 Michael Holzheu
2013-05-24 14:36 ` Vivek Goyal [this message]
2013-05-24 15:06   ` [PATCH 0/2] kdump/mmap: Fix mmap of /proc/vmcore " Michael Holzheu
2013-05-24 15:28     ` Vivek Goyal
2013-05-24 16:46       ` Michael Holzheu
2013-05-24 17:05         ` Vivek Goyal
2013-05-25 13:13           ` Michael Holzheu
2013-05-24 22:44       ` Eric W. Biederman
2013-05-25  0:33         ` Zhang Yanfei
2013-05-25  3:01           ` Eric W. Biederman
2013-05-25  8:31             ` Zhang Yanfei
2013-05-25 12:52               ` Michael Holzheu
2013-05-28 13:55                 ` Vivek Goyal
2013-05-29 11:51                   ` Michael Holzheu
2013-05-29 16:23                     ` Vivek Goyal
2013-05-29 17:12                       ` Michael Holzheu
2013-05-30 15:00                         ` Vivek Goyal
2013-05-30 20:38                     ` Vivek Goyal
2013-05-31 14:21                       ` Michael Holzheu
2013-05-31 16:01                         ` Vivek Goyal
2013-06-03 13:27                           ` Michael Holzheu
2013-06-03 15:59                             ` Vivek Goyal
2013-06-03 16:48                               ` Michael Holzheu
2013-05-28 14:44                 ` Vivek Goyal
2013-05-25 20:36               ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130524143644.GD18218@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=willeke@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).