public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <brgerst@gmail.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>, "H . Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>, Brian Gerst <brgerst@gmail.com>
Subject: [PATCH v2 0/6] x86/boot: Clean up handling of boot_params pointer
Date: Wed, 12 Apr 2023 14:44:56 -0400	[thread overview]
Message-ID: <20230412184502.145289-1-brgerst@gmail.com> (raw)

On entry from the bootloader, RSI contains the pointer to the boot_params
data structure.  The pointer is passed to x86_64_start_kernel(), which
requires preserving RSI all the way though the early boot asm code.
Change it to copy the boot_params data as soon as possible, which also
has the benefit of not needing to remap the real mode data pages if
memory encryption is enabled.

Note: The memory encryption changes are untested due to lack of hardware.

Brian Gerst (6):
  x86/boot: Move sanitize_boot_params()
  x86/boot: Remove extra call to copy_bootdata()
  x86/boot: Clean up get_cmd_line_ptr()
  x86/boot: Move copy_bootdata() to very early boot.
  x86/boot: Use copied boot data in __startup_64()
  x86/boot: Use copied boot data in sme_enable()

 arch/x86/include/asm/mem_encrypt.h |  4 +-
 arch/x86/include/asm/setup.h       |  9 +++--
 arch/x86/kernel/head64.c           | 59 ++++++++++-------------------
 arch/x86/kernel/head_64.S          | 26 +++----------
 arch/x86/kernel/setup.c            |  2 +-
 arch/x86/mm/mem_encrypt_amd.c      | 61 ------------------------------
 arch/x86/mm/mem_encrypt_identity.c | 42 ++++++++++----------
 arch/x86/xen/enlighten_pv.c        |  2 +-
 8 files changed, 58 insertions(+), 147 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-04-12 18:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 18:44 Brian Gerst [this message]
2023-04-12 18:44 ` [PATCH v2 1/6] x86/boot: Move sanitize_boot_params() Brian Gerst
2023-04-12 18:44 ` [PATCH v2 2/6] x86/boot: Remove extra call to copy_bootdata() Brian Gerst
2023-04-12 18:44 ` [PATCH v2 3/6] x86/boot: Clean up get_cmd_line_ptr() Brian Gerst
2023-04-12 18:45 ` [PATCH v2 4/6] x86/boot: Move copy_bootdata() to very early boot Brian Gerst
2023-04-12 18:45 ` [PATCH v2 5/6] x86/boot: Use copied boot data in __startup_64() Brian Gerst
2023-04-12 18:45 ` [PATCH v2 6/6] x86/boot: Use copied boot data in sme_enable() Brian Gerst

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=20230412184502.145289-1-brgerst@gmail.com \
    --to=brgerst@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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