From: Simon Horman <horms@verge.net.au>
To: "Suzuki K. Poulose" <suzuki@in.ibm.com>
Cc: Matthew McClintock <msm@freescale.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] kexec/ppc: Fix kernel program entry point while changing the load addr
Date: Mon, 4 Mar 2013 10:41:52 +0900 [thread overview]
Message-ID: <20130304014152.GB9007@verge.net.au> (raw)
In-Reply-To: <20130303073540.12040.16854.stgit@suzukikp>
[ Cc: linuxppc-dev@lists.ozlabs.org ]
On Sun, Mar 03, 2013 at 01:06:00PM +0530, Suzuki K. Poulose wrote:
> From: Suzuki K. Poulose <suzuki@in.ibm.com>
>
> uImage probe fills the entry point (ep) based on the load_addr
> from the uImage headers. If we change the load_addr, we should
> accordingly update the entry point.
>
> For ELF, calculate the offset of e_entry from the virtual start
> address and add it to the physical start address to find the
> physical address of kernel entry.
>
> i.e,
> pa (e_entry) = pa(phdr[0].p_vaddr) + (e_entry - phdr[0].p_vaddr)
> = kernel_addr + (e_entry - phdr[0].p_vaddr)
Would it be possible for someone to provide a review of this change?
>
> Signed-off-by: Suzuki K. Poulose <suzuki@in.ibm.com>
> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Cc: Matthew McClintock <msm@freescale.com>
> ---
> kexec/arch/ppc/kexec-elf-ppc.c | 12 ++++++++----
> kexec/arch/ppc/kexec-uImage-ppc.c | 6 +++++-
> 2 files changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/kexec/arch/ppc/kexec-elf-ppc.c b/kexec/arch/ppc/kexec-elf-ppc.c
> index 8e408cc..5f63a64 100644
> --- a/kexec/arch/ppc/kexec-elf-ppc.c
> +++ b/kexec/arch/ppc/kexec-elf-ppc.c
> @@ -397,10 +397,14 @@ int elf_ppc_load(int argc, char **argv, const char *buf, off_t len,
> die("Error device tree not loadded to address it was expecting to be loaded too!\n");
> }
>
> - /* set various variables for the purgatory ehdr.e_entry is a
> - * virtual address, we can use kernel_addr which
> - * should be the physical start address of the kernel */
> - addr = kernel_addr;
> + /*
> + * set various variables for the purgatory.
> + * ehdr.e_entry is a virtual address. we know physical start
> + * address of the kernel (kernel_addr). Find the offset of
> + * e_entry from the virtual start address(e_phdr[0].p_vaddr)
> + * and calculate the actual physical address of the 'kernel entry'.
> + */
> + addr = kernel_addr + (ehdr.e_entry - ehdr.e_phdr[0].p_vaddr);
> elf_rel_set_symbol(&info->rhdr, "kernel", &addr, sizeof(addr));
>
> addr = dtb_addr;
> diff --git a/kexec/arch/ppc/kexec-uImage-ppc.c b/kexec/arch/ppc/kexec-uImage-ppc.c
> index e0bc7bb..900cd16 100644
> --- a/kexec/arch/ppc/kexec-uImage-ppc.c
> +++ b/kexec/arch/ppc/kexec-uImage-ppc.c
> @@ -159,15 +159,19 @@ static int ppc_load_bare_bits(int argc, char **argv, const char *buf,
>
> /*
> * If the provided load_addr cannot be allocated, find a new
> - * area.
> + * area. Rebase the entry point based on the new load_addr.
> */
> if (!valid_memory_range(info, load_addr, load_addr + (len + _1MiB))) {
> + int ep_offset = ep - load_addr;
> +
> load_addr = locate_hole(info, len + _1MiB, 0, 0, max_addr, 1);
> if (load_addr == ULONG_MAX) {
> printf("Can't allocate memory for kernel of len %ld\n",
> len + _1MiB);
> return -1;
> }
> +
> + ep = load_addr + ep_offset;
> }
>
> add_segment(info, buf, len, load_addr, len + _1MiB);
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-03-04 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 7:36 [PATCH] kexec/ppc: Fix kernel program entry point while changing the load addr Suzuki K. Poulose
2013-03-04 1:41 ` Simon Horman [this message]
2013-03-04 5:56 ` Suzuki K. Poulose
2013-03-05 1:40 ` Simon Horman
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=20130304014152.GB9007@verge.net.au \
--to=horms@verge.net.au \
--cc=bigeasy@linutronix.de \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msm@freescale.com \
--cc=suzuki@in.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