public inbox for linux-kernel@vger.kernel.org
 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>,
	Andrew Morton <akpm@linux-foundation.org>,
	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 v7 0/5] kdump: Allow ELF header creation in new kernel
Date: Thu, 18 Jul 2013 09:27:57 -0400	[thread overview]
Message-ID: <20130718132757.GA785@redhat.com> (raw)
In-Reply-To: <20130718124004.098b85f4@holzheu>

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. 

Only thing different about s390 is primarily zfcpdump w.r.t handling of
HSA region and creating of elf headers in 2nd kernel.

Thanks
Vivek

  parent reply	other threads:[~2013-07-18 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF6010D9F0.5A45F2CF-ONC1257BAB.002B1F3E-C1257BAB.002B2812@de.ibm.com>
2013-07-17 16:00 ` [PATCH v7 0/5] kdump: Allow ELF header creation in new kernel Michael Holzheu
2013-07-17 21:42   ` Vivek Goyal
2013-07-18 10:40     ` Michael Holzheu
2013-07-18 10:47       ` Martin Schwidefsky
2013-07-18 13:35         ` Vivek Goyal
2013-07-19  6:50           ` Martin Schwidefsky
2013-07-19 13:35             ` Vivek Goyal
2013-07-19 14:20               ` Martin Schwidefsky
2013-07-18 13:27       ` Vivek Goyal [this message]
2013-07-18 14:31         ` Michael Holzheu
2013-07-18 14:38           ` Vivek Goyal
2013-07-16 16:18 Michael Holzheu
2013-07-16 17:24 ` Vivek Goyal
2013-07-17 21:32   ` Andrew Morton

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=20130718132757.GA785@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --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