From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kexec@lists.infradead.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org, Jan Willeke <willeke@de.ibm.com>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v6 3/5] vmcore: Introduce remap_oldmem_pfn_range()
Date: Tue, 16 Jul 2013 17:37:09 +0200 [thread overview]
Message-ID: <20130716173709.3fed4c42@holzheu> (raw)
In-Reply-To: <20130716140418.GB4005@redhat.com>
On Tue, 16 Jul 2013 10:04:18 -0400
Vivek Goyal <vgoyal@redhat.com> wrote:
> On Tue, Jul 16, 2013 at 11:25:27AM +0200, Michael Holzheu wrote:
>
> [..]
> > > > Hello Vivek and Andrew,
> > > >
> > > > We just realized that Hatayama's mmap patches went into v3.11-rc1. This currently
> > > > breaks s390 kdump because of the following two issues:
> > > >
> > > > 1) The copy_oldmem_page() is now used for copying to vmalloc memory
> > > > 2) The mmap() implementation is not compatible with the current
> > > > s390 crashkernel swap:
> > > > See: http://marc.info/?l=kexec&m=136940802511603&w=2
> > > >
> > > > The "kdump: Introduce ELF header in new memory feature" patch series will
> > > > fix both issues for s390.
> > > >
> > > > There is the one small open discussion left:
> > > >
> > > > http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg464856.html
> > > >
> > > > But once we have finished that, would it be possible to get the
> > > > patches in 3.11?
> > >
> > > How about taking mmap() fault handler patches in 3.12. And in 3.11, deny
> > > mmap() on s390 forcing makedumpfile to fall back on read() interface. That
> > > way there will be no regression and mmap() related speedup will show up
> > > in next release on s390.
> >
> > Hello Vivek and Hatayama,
> >
> > But then we still would have to somehow fix the copy_oldmem_page() issue (1).
> >
> > We would prefer to add the current patch series with "#ifndef CONFIG_S390" in
> > the fault handler.
> >
> > @Vivek:
> >
> > Since you are the kdump maintainer, could you tell us which of the both
> > variants you would like to have?
> >
> > static int mmap_vmcore_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
> > {
> > ...
> >
> > #ifndef CONFIG_S390
> > return VM_FAULT_SIGBUS;
> > #endif
>
> I think let us use this one. Kill the process on non-s390 arch if it goes
> into mmap() fault handler.
>
> copy_oldmem_page() using real mode in s390 is an issue for vmalloc region.
> I think post the series again and let us see if Andrew is comfortable
> with it.
Ok great, I will send Andrew the current patch series.
Let's see what happens...
> I suspect it is late.
> IIUC, we do copying in real mode only to cope with HSA region in zfcpdump
> case.
The problem is that with the mmap patches we now use copy_oldmem_page()
to copy the notes from oldmem into the notes_buf which has been allocated
with vmalloc. The s390 version of copy_oldmem_page() bypasses the page
tables and uses real copy. And this does not work on vmalloc memory.
Best Regards,
Michael
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-07-16 15:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 19:32 [PATCH v6 0/5] kdump: Allow ELF header creation in new kernel Michael Holzheu
2013-07-01 19:32 ` [PATCH v6 1/5] vmcore: Introduce ELF header in new memory feature Michael Holzheu
2013-07-02 15:27 ` Vivek Goyal
2013-07-01 19:32 ` [PATCH v6 2/5] s390/vmcore: Use " Michael Holzheu
2013-07-02 16:23 ` Vivek Goyal
2013-07-03 7:59 ` Michael Holzheu
2013-07-03 14:15 ` Vivek Goyal
2013-07-03 14:39 ` Michael Holzheu
2013-07-03 14:50 ` Vivek Goyal
2013-07-01 19:32 ` [PATCH v6 3/5] vmcore: Introduce remap_oldmem_pfn_range() Michael Holzheu
2013-07-02 15:42 ` Vivek Goyal
2013-07-03 13:59 ` Michael Holzheu
2013-07-03 14:16 ` Vivek Goyal
2013-07-15 13:44 ` Michael Holzheu
2013-07-15 14:27 ` Vivek Goyal
2013-07-16 9:25 ` Michael Holzheu
2013-07-16 14:04 ` Vivek Goyal
2013-07-16 15:37 ` Michael Holzheu [this message]
2013-07-16 15:55 ` Vivek Goyal
2013-07-08 5:32 ` HATAYAMA Daisuke
2013-07-08 9:28 ` Michael Holzheu
2013-07-08 14:28 ` Vivek Goyal
2013-07-09 5:49 ` HATAYAMA Daisuke
2013-07-10 8:42 ` Michael Holzheu
2013-07-10 9:50 ` HATAYAMA Daisuke
2013-07-10 11:00 ` Michael Holzheu
2013-07-12 16:02 ` HATAYAMA Daisuke
2013-07-15 9:21 ` Martin Schwidefsky
2013-07-16 0:51 ` HATAYAMA Daisuke
2013-07-10 14:33 ` Vivek Goyal
2013-07-12 11:05 ` HATAYAMA Daisuke
2013-07-15 14:20 ` Vivek Goyal
2013-07-16 0:27 ` HATAYAMA Daisuke
2013-07-16 9:40 ` HATAYAMA Daisuke
2013-07-09 5:31 ` HATAYAMA Daisuke
2013-07-01 19:32 ` [PATCH v6 4/5] s390/vmcore: Implement remap_oldmem_pfn_range for s390 Michael Holzheu
2013-07-01 19:32 ` [PATCH v6 5/5] s390/vmcore: Use vmcore for zfcpdump Michael Holzheu
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=20130716173709.3fed4c42@holzheu \
--to=holzheu@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=vgoyal@redhat.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