From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
loongarch@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-efi@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] efistub: Only link libstub to final vmlinux
Date: Thu, 23 Oct 2025 14:55:05 +0800 [thread overview]
Message-ID: <33612d85-e70b-26da-8460-ea6b9064ce08@loongson.cn> (raw)
In-Reply-To: <CAAhV-H6m5vszCyiF3qi94cpHBPVuqM2xH93D=gfsQqOSYvC-sA@mail.gmail.com>
Hi Josh and Ard,
On 2025/10/20 下午2:55, Huacai Chen wrote:
> On Mon, Oct 20, 2025 at 9:24 AM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
>>
>> Hi Josh, Ard and Huacai,
>>
>> On 2025/10/18 上午1:05, Josh Poimboeuf wrote:
>>
>> ...
>>
>>> But IIUC, the libstub code runs *very* early, and wouldn't show up in a
>>> stack trace anyway, because there are no traces of it on the stack once
>>> it branches to head.S code (which doesn't save the link register).
>>
>> Thanks for your discussions.
>>
>> Are you OK with this current patch?
> For me the current patch is just OK.
We have discussed this a few times but there is almost no consensus
of what should happen next and nothing changes.
Could you please give me a clear reply? Then I can make progress for
the following series:
https://lore.kernel.org/loongarch/20250917112716.24415-1-yangtiezhu@loongson.cn/
Thanks,
Tiezhu
next prev parent reply other threads:[~2025-10-23 6:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 8:55 [PATCH v2] efistub: Only link libstub to final vmlinux Tiezhu Yang
2025-09-28 13:41 ` Ard Biesheuvel
2025-09-28 13:52 ` Huacai Chen
2025-09-28 14:39 ` Ard Biesheuvel
2025-09-28 14:41 ` Ard Biesheuvel
2025-10-09 7:27 ` Tiezhu Yang
2025-10-10 16:25 ` Ard Biesheuvel
2025-10-11 1:13 ` Tiezhu Yang
2025-10-11 2:54 ` Huacai Chen
2025-10-11 3:40 ` Ard Biesheuvel
2025-10-11 7:29 ` Tiezhu Yang
2025-10-11 7:42 ` Huacai Chen
2025-10-11 8:13 ` Tiezhu Yang
2025-10-11 14:48 ` Ard Biesheuvel
2025-10-11 15:01 ` Huacai Chen
2025-10-11 15:58 ` Ard Biesheuvel
2025-10-13 7:34 ` Tiezhu Yang
2025-10-13 14:09 ` Huacai Chen
2025-10-13 14:36 ` Ard Biesheuvel
2025-10-14 16:47 ` Josh Poimboeuf
2025-10-16 14:52 ` Ard Biesheuvel
2025-10-16 15:49 ` Josh Poimboeuf
2025-10-17 11:00 ` Ard Biesheuvel
2025-10-17 16:22 ` Josh Poimboeuf
2025-10-17 16:26 ` Ard Biesheuvel
2025-10-17 17:05 ` Josh Poimboeuf
2025-10-20 1:24 ` Tiezhu Yang
2025-10-20 6:55 ` Huacai Chen
2025-10-23 6:55 ` Tiezhu Yang [this message]
2025-10-23 8:01 ` Huacai Chen
2025-10-23 8:06 ` Ard Biesheuvel
2025-10-26 11:20 ` Huacai Chen
2025-10-28 13:47 ` Ard Biesheuvel
2025-11-10 1:18 ` Tiezhu Yang
2025-11-10 7:00 ` Huacai Chen
2025-11-11 16:49 ` Ard Biesheuvel
2025-11-11 18:00 ` Josh Poimboeuf
2025-11-15 3:16 ` Huacai Chen
2025-11-17 11:33 ` Will Deacon
2025-11-21 2:09 ` Paul Walmsley
2025-11-21 14:36 ` Huacai Chen
2025-11-22 11:04 ` Tiezhu Yang
2025-11-23 2:29 ` Huacai Chen
2025-11-23 3:37 ` Tiezhu Yang
2025-11-25 1:49 ` Josh Poimboeuf
2025-11-28 10:11 ` Huacai Chen
2025-09-30 2:52 ` Huacai Chen
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=33612d85-e70b-26da-8460-ea6b9064ce08@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
/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