From: Conor Dooley <conor.dooley@microchip.com>
To: Nylon Chen <nylon.chen@sifive.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<jszhang@kernel.org>, <ajones@ventanamicro.com>,
<aou@eecs.berkeley.edu>, <palmer@dabbelt.com>,
<paul.walmsley@sifive.com>, <greentime.hu@sifive.com>,
<zong.li@sifive.com>, <nylon7717@gmail.com>
Subject: Re: [PATCH v2] RISC-V: Support 32_PCREL relocation type in kernel module
Date: Thu, 15 Jun 2023 08:37:59 +0100 [thread overview]
Message-ID: <20230615-unvisited-deceit-9beab8ce987a@wendy> (raw)
In-Reply-To: <20230615072302.25638-1-nylon.chen@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
Hey Nylon, thanks for the update.
On Thu, Jun 15, 2023 at 03:23:02PM +0800, Nylon Chen wrote:
> Fix the 'unsupported relocation type' error caused by
> enabling the -fasynchronous-unwind-tables flag,
> which generates relocation types that are not supported.
What commit adds the -fasynchronous-unwind-tables flag?
Should there be a Fixes: tag for that commit?
Cheers,
Conor.
>
> Signed-off-by: Nylon Chen <nylon.chen@sifive.com>
> Reviewed-by: Zong Li <zong.li@sifive.com>
> ---
> Changed in v2:
> - add commit message.
>
> arch/riscv/kernel/module.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/riscv/kernel/module.c b/arch/riscv/kernel/module.c
> index 7c651d55fcbd..65be0360a494 100644
> --- a/arch/riscv/kernel/module.c
> +++ b/arch/riscv/kernel/module.c
> @@ -310,6 +310,15 @@ static int apply_r_riscv_sub64_rela(struct module *me, u32 *location,
> return 0;
> }
>
> +static int apply_r_riscv_pcrel_32_rela(struct module *me, u32 *location,
> + Elf_Addr v)
> +{
> + ptrdiff_t offset = (void *)v - (void *)location;
> +
> + *location = (*location & 0xffff0000) | (offset & 0xffff);
> + return 0;
> +}
> +
> static int (*reloc_handlers_rela[]) (struct module *me, u32 *location,
> Elf_Addr v) = {
> [R_RISCV_32] = apply_r_riscv_32_rela,
> @@ -335,6 +344,7 @@ static int (*reloc_handlers_rela[]) (struct module *me, u32 *location,
> [R_RISCV_SUB16] = apply_r_riscv_sub16_rela,
> [R_RISCV_SUB32] = apply_r_riscv_sub32_rela,
> [R_RISCV_SUB64] = apply_r_riscv_sub64_rela,
> + [R_RISCV_32_PCREL] = apply_r_riscv_pcrel_32_rela,
> };
>
> int apply_relocate_add(Elf_Shdr *sechdrs, const char *strtab,
> --
> 2.40.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-15 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 7:23 Nylon Chen
2023-06-15 7:36 ` Andreas Schwab
2023-06-15 7:37 ` Conor Dooley [this message]
[not found] ` <CAHh=Yk_=oZJ6eY3jJzLavub5rGsvY=MKv4tGXeiqkz+rgJHwDQ@mail.gmail.com>
2023-06-15 8:07 ` Andreas Schwab
2023-06-15 8:11 ` Conor Dooley
2023-06-15 8:43 ` Nylon Chen
2023-06-15 9:11 ` Andreas Schwab
2023-06-15 9:47 ` Nylon Chen
2023-08-21 7:51 ` Nylon Chen
2023-08-21 8:01 ` Andreas Schwab
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=20230615-unvisited-deceit-9beab8ce987a@wendy \
--to=conor.dooley@microchip.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=greentime.hu@sifive.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nylon.chen@sifive.com \
--cc=nylon7717@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=zong.li@sifive.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
all inboxes | Powered by JetHome®