Received-SPF: pass (google.com: domain of linux-kernel+bounces-149958-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Thu, 18 Apr 2024 13:14:35 +0200
From: Borislav Petkov <bp@alien8.de>
To: Nathan Chancellor <nathan@kernel.org>, tglx@linutronix.de, mingo@redhat.com,
 dave.hansen@linux.intel.com
CC: x86@kernel.org, hpa@zytor.com, ndesaulniers@google.com, morbo@google.com,
 justinstitt@google.com, song@kernel.org, ribalda@chromium.org,
 linux-kernel@vger.kernel.org, llvm@lists.linux.dev, patches@lists.linux.dev,
 ns <0n-s@users.noreply.github.com>
Subject: =?US-ASCII?Q?Re=3A_=5BPATCH_0/2=5D_x86/purgatory=3A_Avoi?=
 =?US-ASCII?Q?d_kexec_runtime_warning_with_LLVM_18?=
User-Agent: K-9 Mail for Android
In-Reply-To: <20240417-x86-fix-kexec-with-llvm-18-v1-0-5383121e8fb7@kernel.org>
References: <20240417-x86-fix-kexec-with-llvm-18-v1-0-5383121e8fb7@kernel.org>
Message-ID: <46343CD5-24D6-46BF-92A7-0B0FA0E6937D@alien8.de>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

On April 17, 2024 11:53:44 PM GMT+02:00, Nathan Chancellor <nathan@kernel=
=2Eorg> wrote:
>Hi all,
>
>After LLVM commit d8a04398f949 ("Reland [X86] With large code model, put
>functions into =2Eltext with large section flag (#73037)") [1], which
>landed in the 18=2Ex cycle, there is a runtime warning when loading a
>kernel via kexec due to the presence of two text sections (=2Etext and
>=2Eltext)=2E

How much of this silliness should we expect now for other parts of the ker=
nel?

Can we turn this off?

Why does llvm enforce =2Eltext for large code models and why gcc doesn't d=
o that? Why does llvm need to do that, what requirement dictates that?

Thx=2E

--=20
Sent from a small device: formatting sucks and brevity is inevitable=2E