Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Xie Yuanbin <xieyuanbin1@huawei.com>
To: <egg12138@foxmail.com>
Cc: <xieyuanbin1@huawei.com>, <jpoimboe@kernel.org>,
	<linusw@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-modules@vger.kernel.org>,
	<linux@armlinux.org.uk>, <petr.pavlu@suse.com>,
	<pmladek@suse.com>, <rostedt@goodmis.org>
Subject: Re: [PATCH v3] ARM: module.lds: fix unwind metadata for merged .text sections
Date: Fri, 7 Aug 2026 10:13:28 +0800	[thread overview]
Message-ID: <20260807021328.36897-1-xieyuanbin1@huawei.com> (raw)
In-Reply-To: <tencent_EB65B78E967A5FF9DD2A591A86A6BD5B1107@qq.com>

On Thu, 6 Aug 2026 22:29:03 +0800, Xiao Junzhe wrote:
> My reason for including the exact matches is slightly different.
> AAELF32 defines these section namespaces as .ARM.exidx* and
> .ARM.extab*; it does not require all ABI-conforming object producers to
> use the same naming convention as GNU as and LLVM.
>
> For example, another producer or future version of GNU/LLVM impl for `as`
> could validly use:
>
>     .text -> .ARM.exidx.text

I have thought about it again. For other sections, the mapping is
as follows:
	.xxx -> .ARM.exidx.xxx

So, if there is an ".ARM.exidx.text", it must be from ".text", and adding
".ARM.exidx.text" will not cause any other harm. We only need
to ensure that the merging of the ".text*" sections is consistent
with the merging of the ".ARM.exidx*" sections, and the current patch
already satisfies this requirement.

I have no other questions about this, so:
Reviewed-by: Xie Yuanbin <xieyuanbin1@huawei.com>
Tested-by: Xie Yuanbin <xieyuanbin1@huawei.com>

Also, don't forget to submit your patch to Russell's
patch tracker:
Link: https://www.armlinux.org.uk/developer/patches/

Thanks.


      reply	other threads:[~2026-08-07  2:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 15:46 [PATCH v3] ARM: module.lds: fix unwind metadata for merged .text sections Egg12138
2026-07-27  7:47 ` Ju Nan
2026-08-06  9:34 ` Petr Pavlu
2026-08-06 13:02 ` Xie Yuanbin
2026-08-06 14:29   ` Xiao Junzhe
2026-08-07  2:13     ` Xie Yuanbin [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=20260807021328.36897-1-xieyuanbin1@huawei.com \
    --to=xieyuanbin1@huawei.com \
    --cc=egg12138@foxmail.com \
    --cc=jpoimboe@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=petr.pavlu@suse.com \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.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