public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20240301185618.19663-1-bp@alien8.de> (raw)

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(-)

-- 
2.43.0


             reply	other threads:[~2024-03-01 18:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 18:56 Borislav Petkov [this message]
2024-03-01 18:56 ` [RFC PATCH 1/2] Revert "x86/kexec/64: Prevent kexec from 5-level paging to a 4-level only kernel" Borislav Petkov
2024-03-04 10:51   ` Baoquan He
2024-03-04 11:11     ` Borislav Petkov
2024-03-05  3:43       ` Baoquan He
2024-03-05 11:55         ` Borislav Petkov
2024-03-06  4:02           ` Baoquan He
2024-03-01 18:56 ` [RFC PATCH 2/2] Revert "x86/boot: Add xloadflags bits to check for 5-level paging support" Borislav Petkov

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=20240301185618.19663-1-bp@alien8.de \
    --to=bp@alien8.de \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    /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