Received-SPF: pass (google.com: domain of linux-kernel+bounces-88967-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: Borislav Petkov <bp@alien8.de>
To: Baoquan He <bhe@redhat.com>
Cc: X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/2] x86/kexec: Revert 5level dynamic switching
Date: Fri,  1 Mar 2024 19:56:16 +0100
Message-ID: <20240301185618.19663-1-bp@alien8.de>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

From: "Borislav Petkov (AMD)" <bp@alien8.de>

Hi,

I think this is silly - both 1st and second, the-kexec'ed kernel would
either have CONFIG_X86_5LEVEL enabled or not - why would this be
different.

And this'll become even more the case in the future.

So remove this silly stuff.

Unless there's a valid use case, which I'm willing to hear. Those commit
messages don't say anything about it.

Thx.

Borislav Petkov (AMD) (2):
  Revert "x86/kexec/64: Prevent kexec from 5-level paging to a 4-level
    only kernel"
  Revert "x86/boot: Add xloadflags bits to check for 5-level paging
    support"

 arch/x86/boot/header.S                | 12 +-----------
 arch/x86/include/uapi/asm/bootparam.h |  2 --
 arch/x86/kernel/kexec-bzimage64.c     |  5 -----
 3 files changed, 1 insertion(+), 18 deletions(-)

--=20
2.43.0