mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/boot for v7.4-rc1
Date: Mon, 19 Oct 2026 17:24:46 -0700	[thread overview]
Message-ID: <20261020002446.GAata0znTHnFvT5ePT@fat_crate.local> (raw)

Hi Linus,

please pull the x86/boot lineup for v7.4-rc1.

Thx.

---

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_boot_for_v7.4_rc1

for you to fetch changes up to dc2a1671d983d26b8ea5a4c5de9c5a028707f40b:

  x86/boot: Drop unused implementation of panic() (2026-09-28 18:07:34 -0700)

----------------------------------------------------------------
- Rework the early decompressor some and drop the version of panic() there
  which used vsnprintf() supplied by the EFI stub even in legacy boot cases,
  where the EFI stub is not present. By Ard Biesheuvel

- Fix unbootable VMs with CONFIG_PVH=y and CONFIG_KASAN_GENERIC=y where the
  compiler decides not to inline __builtin_{memcmp,memset}(). Force the
  inlining with the kernel's own __inline_* versions; by Mauricio Faria de
  Oliveira

- Cleanups and fixlets

----------------------------------------------------------------
Ard Biesheuvel (3):
      x86/tdx: Share tdx_panic() with the EFI stub
      x86/boot: Move unaccepted memory handling out of the decompressor
      x86/boot: Drop unused implementation of panic()

Mauricio Faria de Oliveira (4):
      x86/boot: Remove redundant "cc" clobber in memcmp() and document it
      x86/asm, x86/boot: Carve out inline memcmp() into a separate header
      x86/asm: Group inline string functions
      x86/pvh: Really inline memcmp() and memset() to fix unbootable VMs

Thorsten Blum (1):
      x86/boot: Use BASE_BAUD and DEFAULT_SERIAL_PORT

 arch/x86/boot/compressed/error.c        | 19 ------------
 arch/x86/boot/compressed/error.h        |  1 -
 arch/x86/boot/compressed/mem.c          | 42 --------------------------
 arch/x86/boot/compressed/sev.h          |  2 --
 arch/x86/boot/compressed/tdx-shared.c   |  2 ++
 arch/x86/boot/early_serial_console.c    | 13 ++++-----
 arch/x86/boot/string.c                  | 13 ++-------
 arch/x86/coco/tdx/tdx-shared.c          | 31 ++++++++++++++++++++
 arch/x86/coco/tdx/tdx.c                 | 35 ----------------------
 arch/x86/include/asm/cpuid/api.h        |  2 +-
 arch/x86/include/asm/sev.h              |  2 ++
 arch/x86/include/asm/shared/string.h    | 52 +++++++++++++++++++++++++++++++++
 arch/x86/include/asm/shared/tdx.h       |  1 +
 arch/x86/include/asm/string.h           | 21 +------------
 arch/x86/platform/pvh/enlighten.c       |  3 +-
 drivers/firmware/efi/libstub/x86-stub.c | 39 +++++++++++++++++++++++++
 16 files changed, 138 insertions(+), 140 deletions(-)
 create mode 100644 arch/x86/include/asm/shared/string.h


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

                 reply	other threads:[~2026-10-20  0:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261020002446.GAata0znTHnFvT5ePT@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®