From: Jinyang He <hejinyang@loongson.cn>
To: Bibo Mao <maobibo@loongson.cn>, Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Xi Zhang <zhangxi@kylinos.cn>,
Xianglai Li <lixianglai@loongson.cn>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] LoongArch: Handle special PC in unwind_next_frame()
Date: Thu, 27 Nov 2025 10:53:19 +0800 [thread overview]
Message-ID: <226cffcb-2302-8afb-8be6-9cab2176d15b@loongson.cn> (raw)
In-Reply-To: <7ddd6efc-e7ad-b2f8-9a4d-5ca1cad9e74d@loongson.cn>
On 2025-11-27 09:53, Bibo Mao wrote:
>
> Just be curious, it is the same orc unwind method. why is clean with
> file arch/x86/kernel/unwind_orc.c, however there is special handling
> bt_address() in file arch/loongarch/kernel/unwind_orc.c ?
>
I'm not familiar with x86. Does it also copies exception handler to
other address like LoongArch? When backtrace to the copied exception
handler, its ORC info is not collected. The bt_address finds a
shadow PC to get the right ORC info and go on.
Thanks,
Jinyang
next prev parent reply other threads:[~2025-11-27 2:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 6:33 Tiezhu Yang
2025-11-25 8:08 ` Huacai Chen
2025-11-25 8:54 ` Tiezhu Yang
2025-11-25 9:05 ` Huacai Chen
2025-11-26 5:36 ` Tiezhu Yang
2025-11-25 10:52 ` Jinyang He
2025-11-26 6:08 ` Tiezhu Yang
2025-11-26 6:28 ` Tiezhu Yang
2025-11-26 9:09 ` Tiezhu Yang
2025-11-26 9:27 ` Huacai Chen
2025-11-27 1:32 ` Tiezhu Yang
2025-11-26 9:56 ` Bibo Mao
2025-11-27 1:39 ` Tiezhu Yang
2025-11-27 1:53 ` Bibo Mao
2025-11-27 2:53 ` Jinyang He [this message]
2025-11-27 2:58 ` Bibo Mao
2025-12-09 2:08 ` Tiezhu Yang
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=226cffcb-2302-8afb-8be6-9cab2176d15b@loongson.cn \
--to=hejinyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixianglai@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=yangtiezhu@loongson.cn \
--cc=zhangxi@kylinos.cn \
/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®