From: Andreas Schwab <schwab@suse.de>
To: Nylon Chen <nylon.chen@sifive.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
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: Mon, 21 Aug 2023 10:01:33 +0200 [thread overview]
Message-ID: <mvmy1i4ako2.fsf@suse.de> (raw)
In-Reply-To: <CAHh=Yk8upMOdhma4EDZj_TsA2rf8=MQVrP2sidhmwBh3G-ix-Q@mail.gmail.com> (Nylon Chen's message of "Mon, 21 Aug 2023 15:51:14 +0800")
On Aug 21 2023, Nylon Chen wrote:
> If RISC-V were to support the unwind table in the future, would we
> need to re-enable it? Would this require implementing related
> changes(module relocation type handler) at that time?
I'm not quite sure I understand your question. Nothing in the kernel
makes use of unwind tables on RISC-V, so there is no point in generating
them.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-08-21 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 7:23 [PATCH v2] RISC-V: Support 32_PCREL relocation type in kernel module Nylon Chen
2023-06-15 7:36 ` Andreas Schwab
2023-06-15 7:37 ` Conor Dooley
[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 [this message]
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=mvmy1i4ako2.fsf@suse.de \
--to=schwab@suse.de \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--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