Re: [PATCH v7 0/5] kdump: Allow ELF header creation in new kernel

Michael Holzheu
2013-07-18T14:31:50Z

On Thu, 18 Jul 2013 09:27:57 -0400
Vivek Goyal <vgoyal@redhat.com> wrote:

> On Thu, Jul 18, 2013 at 12:40:04PM +0200, Michael Holzheu wrote:
> > On Wed, 17 Jul 2013 17:42:07 -0400
> > Vivek Goyal <vgoyal@redhat.com> wrote:
> > > On Wed, Jul 17, 2013 at 06:00:49PM +0200, Michael Holzheu wrote:
> >
> > [snip]
> >
> > > > But this is all additional effort now and would not be necessary if we
> > > > integrate this patch series in 3.11.
> > > >
> > > > Perhaps we should let Andrew decide here.
> > >
> > > Hi Michael,
> > >
> > > Given the fact that andrew too prefers a fix to get s390 working at this
> > > stage can we modify s390 copy_from_oldmem() to be able to copy to
> > > vmalloc() memory area.
> > >
> > > For mmap(), let us disable it on s390. And rest of the cleanups w.r.t
> > > ELF header swap etc, let us now target that for 3.12.
> > >
> > > Sounds reasonable?
> >
> > Hi Vivek,
> >
> > Ok this is not our preferred solution but we can't expect that life is
> > always easy ;-)
> >
> > Our s390 kernel maintainer Martin Schwidefsky agreed to send the following
> > two patches upstream for 3.11:
> >
> > * s390/kdump: Disable mmap for s390
> > * s390/kdump: Allow copy_oldmem_page() copy to virtual memory
> >
> > @Andrew:
> >
> > Would you then take the "ELF header in new memory" patch series for 3.12?
>
> Hi Michael,
>
> Once this patch series gets merged for 3.12, can we first do some cleanup
> of s390 code before we do further development there. Basically there is
> no reason that s390 kdump should be any different than x86. So all the
> logic of OLD base can go away.

Hello Vivek,

You mean that we first integrate the agreed "ELF header in new memory"
patch series, then do the cleanup, and after that we discuss the further
development (storage keys)?

Michael