[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <40e60857-8e02-cf5e-7804-453b406b0b8b@loongson.cn>
Date: Thu, 4 Sep 2025 10:15:31 +0800
From: Tiezhu Yang <yangtiezhu@...ngson.cn>
To: Josh Poimboeuf <jpoimboe@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>, Huacai Chen
<chenhuacai@...nel.org>, Nathan Chancellor <nathan@...nel.org>,
loongarch@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/3] objtool/LoongArch: Fix fall through warning about
efi_boot_kernel()
On 2025/9/4 上午3:17, Josh Poimboeuf wrote:
> On Mon, Sep 01, 2025 at 04:31:36PM +0800, Tiezhu Yang wrote:
>> On 2025/9/1 下午4:16, Peter Zijlstra wrote:
>>> On Mon, Sep 01, 2025 at 03:21:54PM +0800, Tiezhu Yang wrote:
>>>> When compiling with LLVM and CONFIG_LTO_CLANG is set, there exists
>>>> the following objtool warning:
...
>> Josh suggested to do something so that the EFI stub code isn't linked into
>> vmlinux.o [2], it needs to modify the link process and seems too
>> complicated and expensive for this warning to some extent.
>>
>> So I did this change for objtool.
>
> I don't like adding these workarounds to objtool. Is it really that
> complicated to link efistub separately? That seems like the proper
> design. vmlinux.o should only have real kernel code.
OK, I see. If this is the only proper direction, I will do it
in the next version.
Thanks,
Tiezhu
Powered by blists - more mailing lists