From: Pratyush Anand <panand@redhat.com>
To: Geoff Levand <geoff@infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Simon Horman <horms@verge.net.au>,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/4] arm64: Add support for binary image files
Date: Fri, 29 Jul 2016 09:05:14 +0530 [thread overview]
Message-ID: <20160729033514.GC27150@localhost.localdomain> (raw)
In-Reply-To: <1469729083.16559.26.camel@infradead.org>
Hi Geoff,
On 28/07/2016:11:04:43 AM, Geoff Levand wrote:
> Hi Pratyush,
>
> On Thu, 2016-07-28 at 09:31 +0530, Pratyush Anand wrote:
> > On 26/07/2016:08:18:57 PM, Geoff Levand wrote:
>
> > You removed page_offset calculation in rework.
> > I am unable to understand that how arm64_mem.page_offset will be filled up now
> > for binary image case.
> >
> > I think, we still need to keep page_offset user input.
>
> The current kernel linker scripts are setup to output virtual
> address values to the vmlinux elf file.
>
> To load the elf sections of vmlinux using the provided elf
> file loader, elf_exec_load(), we need to convert those elf
> header values to physical addresses since we work with
> physical addresses in the kernel's kimage structure.
>
> That conversion is
>
> p = v - page_offset + phys_offset;
>
> We get phys_offset from the memory ranges, and we calculate
> page_offset from the elf header info.
>
> As for the binary image file, we load that with
> add_segment_phys_virt(), which can put the binary data of the
> Image file into memory at a physical address we specify:
>
> image_base = phys_offset + text_offset.
>
> phys_offset is again from the memory ranges, and text_offset
> from the arm64 image header.
>
>
> > You may take following
> > two patches which does this, or you may leave binary image support patch which I
> > will send after your patches are merged.
> >
> > https://github.com/pratyushanand/kexec-tools/commit/5b7e49a75d1d6cd4ac846f50ff10275fd54cb545
>
> This one may be useful, for debugging if anything.
>
> > https://github.com/pratyushanand/kexec-tools/commit/a0ce0ce673755c4061c1f081170a3a75dfa1d1fb
>
> We do not need, nor want, a PAGE_OFFSET option.
See kexec/crashdump-elf.c:FUNC()
We have:
223 phdr->p_vaddr = phys_to_virt(elf_info, mstart);
Now, if we do not have page_offset then we will not have correct p_vaddr, and
then vmcore-dmesg/vmcore-dmesg.c:vaddr_to_offset() fails with
No program header covering vaddr 0xfffffc0008c312f0found kexec bug?
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] arm64: Add support for binary image files
Date: Fri, 29 Jul 2016 09:05:14 +0530 [thread overview]
Message-ID: <20160729033514.GC27150@localhost.localdomain> (raw)
In-Reply-To: <1469729083.16559.26.camel@infradead.org>
Hi Geoff,
On 28/07/2016:11:04:43 AM, Geoff Levand wrote:
> Hi Pratyush,
>
> On Thu, 2016-07-28 at 09:31 +0530, Pratyush Anand wrote:
> > On 26/07/2016:08:18:57 PM, Geoff Levand wrote:
>
> > You removed page_offset calculation in rework.
> > I am unable to understand that how arm64_mem.page_offset will be filled up now
> > for binary image case.
> >
> > I think, we still need to keep page_offset user input.
>
> The current kernel linker scripts are setup to output virtual
> address values to the vmlinux elf file.
>
> To load the elf sections of vmlinux using the provided elf
> file loader, elf_exec_load(), we need to convert those elf
> header values to physical addresses since we work with
> physical addresses in the kernel's kimage structure.
>
> That conversion is
>
> p = v - page_offset + phys_offset;
>
> We get phys_offset from the memory ranges, and we calculate
> page_offset from the elf header info.
>
> As for the binary image file, we load that with
> add_segment_phys_virt(), which can put the binary data of the
> Image file into memory at a physical address we specify:
>
> image_base = phys_offset + text_offset.
>
> phys_offset is again from the memory ranges, and text_offset
> from the arm64 image header.
>
>
> > You may take following
> > two patches which does this, or you may leave binary image support patch which I
> > will send after your patches are merged.
> >
> > https://github.com/pratyushanand/kexec-tools/commit/5b7e49a75d1d6cd4ac846f50ff10275fd54cb545
>
> This one may be useful, for debugging if anything.
>
> > https://github.com/pratyushanand/kexec-tools/commit/a0ce0ce673755c4061c1f081170a3a75dfa1d1fb
>
> We do not need, nor want, a PAGE_OFFSET option.
See kexec/crashdump-elf.c:FUNC()
We have:
223 phdr->p_vaddr = phys_to_virt(elf_info, mstart);
Now, if we do not have page_offset then we will not have correct p_vaddr, and
then vmcore-dmesg/vmcore-dmesg.c:vaddr_to_offset() fails with
No program header covering vaddr 0xfffffc0008c312f0found kexec bug?
~Pratyush
next prev parent reply other threads:[~2016-07-29 3:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 20:18 [PATCH v2 0/4] arm64 kexec-tools patches Geoff Levand
2016-07-26 20:18 ` Geoff Levand
2016-07-26 20:18 ` [PATCH v2 2/4] kexec: Add common device tree routines Geoff Levand
2016-07-26 20:18 ` Geoff Levand
2016-07-26 20:18 ` [PATCH v2 3/4] arm64: Add arm64 kexec support Geoff Levand
2016-07-26 20:18 ` Geoff Levand
2016-07-28 4:10 ` Pratyush Anand
2016-07-28 4:10 ` Pratyush Anand
2016-07-28 17:33 ` Geoff Levand
2016-07-28 17:33 ` Geoff Levand
2016-07-26 20:18 ` [PATCH v2 1/4] kexec: (bugfix) calc correct end address of memory ranges in device tree Geoff Levand
2016-07-26 20:18 ` Geoff Levand
2016-07-26 20:18 ` [PATCH v2 4/4] arm64: Add support for binary image files Geoff Levand
2016-07-26 20:18 ` Geoff Levand
2016-07-28 4:01 ` Pratyush Anand
2016-07-28 4:01 ` Pratyush Anand
2016-07-28 18:04 ` Geoff Levand
2016-07-28 18:04 ` Geoff Levand
2016-07-29 3:35 ` Pratyush Anand [this message]
2016-07-29 3:35 ` Pratyush Anand
2016-07-29 17:02 ` Geoff Levand
2016-07-29 17:02 ` Geoff Levand
2016-07-29 17:15 ` Pratyush Anand
2016-07-29 17:15 ` Pratyush Anand
2016-07-29 17:19 ` Geoff Levand
2016-07-29 17:19 ` Geoff Levand
2016-08-04 4:51 ` AKASHI Takahiro
2016-08-04 4:51 ` AKASHI Takahiro
2016-08-04 5:11 ` Pratyush Anand
2016-08-04 5:11 ` Pratyush Anand
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=20160729033514.GC27150@localhost.localdomain \
--to=panand@redhat.com \
--cc=geoff@infradead.org \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=takahiro.akashi@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.