From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
kexec@lists.infradead.org, Jan Willeke <willeke@de.ibm.com>,
linux-kernel@vger.kernel.org,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH v6 2/5] s390/vmcore: Use ELF header in new memory feature
Date: Wed, 3 Jul 2013 16:39:44 +0200 [thread overview]
Message-ID: <20130703163944.70319e0a@holzheu> (raw)
In-Reply-To: <20130703141529.GB1460@redhat.com>
On Wed, 3 Jul 2013 10:15:29 -0400
Vivek Goyal <vgoyal@redhat.com> wrote:
> On Wed, Jul 03, 2013 at 09:59:13AM +0200, Michael Holzheu wrote:
> > On Tue, 2 Jul 2013 12:23:23 -0400
> > Vivek Goyal <vgoyal@redhat.com> wrote:
> >
> > > On Mon, Jul 01, 2013 at 09:32:36PM +0200, Michael Holzheu wrote:
> > >
> > > [..]
> > > > +ssize_t elfcorehdr_read(char *buf, size_t count, u64 *ppos)
> > > > +{
> > > > + void *src = (void *)(unsigned long)*ppos;
> > > > +
> > > > + src = elfcorehdr_newmem ? src : src - OLDMEM_BASE;
> > >
> > > Seriously, we need to get rid of all this OLDMEM_BASE logic in s390
> > > specific code. For regular kdump, it is no different than x86. Only
> > > special handling required for zfcpdump for HSA region.
> > >
> > > Why do we need above. Is it to cover the case where elfcorehdr have
> > > been prepared by user space? Are elf headers initially stored in
> > > reserved region and then swapped. Why do we need to swap these or
> > > why kexec-tools could not take care of swapping it.
> >
> > I know it is confusing. The "src - OLDMEM_BASE" term is currently
> > needed because of the swap issue that we have discussed already. We
> > load the ELF header into reserved memory
> > [OLDMEM_BASE, OLDMEM_BASE + OLDMEM_SIZE] that is swapped with
> > [0, OLDMEM_SIZE]. So the ELF header address has to be adjusted.
>
> Can't kexec-tools could easily do this swapping and modify elfcorehdr=
> command line accordingly so that second kernel does not have to do
> swapping for ELF headers.
>
> And for PT_LOAD segment swapping, we could use ELF header swapping trick
> (again in kexec-tools).
>
> After above two changes I think all the OLD_MEMBASE magic will go away
> from s390 code and only HSA region special handling will remain.
>
> This brings it inline with x86 code and it becomes easier to understand
> the s390 code. Otherwise there so may special corner cases that it is
> easy to get lost.
Right, I agree that it is possible to do the swap in the kexec tool.
Then we would load in the kexec tool the ELF header to address
"OLDMEM_BASE + addr" (or "crashkernel base + addr") and would specify
the kernel parameter as "elfcorehdr=addr".
Currently we specify "elfcorehdr=OLDMEM_BASE + addr" and the kernel
reverses the swap.
Michael
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-07-03 14:40 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 [this message]
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
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=20130703163944.70319e0a@holzheu \
--to=holzheu@linux.vnet.ibm.com \
--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