From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: He Ying <heying24@huawei.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
nathan@kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Fix kernel-jump address for ppc64 wrapper boot
Date: Tue, 8 Jun 2021 06:55:35 +0200 [thread overview]
Message-ID: <c80f69d0-44b0-24a6-ce4f-ed5a40514597@csgroup.eu> (raw)
In-Reply-To: <20210604092228.199588-1-heying24@huawei.com>
Le 04/06/2021 à 11:22, He Ying a écrit :
> From "64-bit PowerPC ELF Application Binary Interface Supplement 1.9",
> we know that the value of a function pointer in a language like C is
> the address of the function descriptor and the first doubleword
> of the function descriptor contains the address of the entry point
> of the function.
>
> So, when we want to jump to an address (e.g. addr) to execute for
> PPC-elf64abi, we should assign the address of addr *NOT* addr itself
> to the function pointer or system will jump to the wrong address.
>
> Link: https://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html#FUNC-DES
> Signed-off-by: He Ying <heying24@huawei.com>
> ---
> arch/powerpc/boot/main.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/powerpc/boot/main.c b/arch/powerpc/boot/main.c
> index cae31a6e8f02..50fd7f11b642 100644
> --- a/arch/powerpc/boot/main.c
> +++ b/arch/powerpc/boot/main.c
> @@ -268,7 +268,16 @@ void start(void)
> if (console_ops.close)
> console_ops.close();
>
> +#ifdef CONFIG_PPC64_BOOT_WRAPPER
This kind of need doesn't desserve a #ifdef, see
https://www.kernel.org/doc/html/latest/process/coding-style.html#conditional-compilation
You can do:
kentry = (kernel_entry_t)(IS_ENABLED(CONFIG_PPC64_BOOT_WRAPPER) ? &vmlinux.addr : vmlinux.addr);
Or, if you prefer something less compact:
if (IS_ENABLED(CONFIG_PPC64_BOOT_WRAPPER))
kentry = (kernel_entry_t) &vmlinux.addr;
else
kentry = (kernel_entry_t) vmlinux.addr;
> + /*
> + * For PPC-elf64abi, the value of a function pointer is the address
> + * of the function descriptor. And the first doubleword of a function
> + * descriptor contains the address of the entry point of the function.
> + */
> + kentry = (kernel_entry_t) &vmlinux.addr;
> +#else
> kentry = (kernel_entry_t) vmlinux.addr;
> +#endif
> if (ft_addr) {
> if(platform_ops.kentry)
> platform_ops.kentry(ft_addr, vmlinux.addr);
>
next prev parent reply other threads:[~2021-06-08 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 9:22 He Ying
2021-06-08 4:55 ` Christophe Leroy [this message]
2021-06-08 11:03 ` He Ying
2021-06-08 5:26 ` Oliver O'Halloran
2021-06-08 6:33 ` He Ying
2021-06-08 7:29 ` Oliver O'Halloran
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=c80f69d0-44b0-24a6-ce4f-ed5a40514597@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=benh@kernel.crashing.org \
--cc=heying24@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®