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/urgent for v6.13-rc1
Date: Sun, 1 Dec 2024 11:49:21 +0100 [thread overview]
Message-ID: <20241201104921.GAZ0w_Mev3hhUdkHHr@fat_crate.local> (raw)
Hi Linus,
please pull the x86/urgent lineup for v6.13-rc1.
Thx.
---
The following changes since commit be4202228e685d580d75ac7597c0e7e50a63dd6c:
Merge tag 'x86_tdx_for_6.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2024-11-22 13:07:19 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/x86_urgent_for_v6.13_rc1
for you to fetch changes up to ff6cdc407f4179748f4673c39b0921503199a0ad:
x86/CPU/AMD: Terminate the erratum_1386_microcode array (2024-11-26 15:12:00 +0100)
----------------------------------------------------------------
- Add a terminating zero end-element to the array describing AMD CPUs affected
by erratum 1386 so that the matching loop actually terminates instead of
going off into the weeds
- Update the boot protocol documentation to mention the fact that the
preferred address to load the kernel to is considered in the relocatable
kernel case too
- Flush the memory buffer containing the microcode patch after applying
microcode on AMD Zen1 and Zen2, to avoid unnecessary slowdowns
- Make sure the PPIN CPU feature flag is cleared on all CPUs if PPIN has been
disabled
----------------------------------------------------------------
Andy Shevchenko (1):
x86/Documentation: Update algo in init_size description of boot protocol
Borislav Petkov (AMD) (2):
x86/mm: Carve out INVLPG inline asm for use by others
x86/microcode/AMD: Flush patch buffer mapping after application
Sebastian Andrzej Siewior (1):
x86/CPU/AMD: Terminate the erratum_1386_microcode array
Tony Luck (1):
x86/cpu: Fix PPIN initialization
Documentation/arch/x86/boot.rst | 17 +++++++++++++----
arch/x86/include/asm/tlb.h | 4 ++++
arch/x86/kernel/cpu/amd.c | 1 +
arch/x86/kernel/cpu/common.c | 2 +-
arch/x86/kernel/cpu/microcode/amd.c | 25 ++++++++++++++++++++-----
arch/x86/mm/tlb.c | 3 ++-
6 files changed, 41 insertions(+), 11 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2024-12-01 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 10:49 Borislav Petkov [this message]
2024-12-01 20:50 ` pr-tracker-bot
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=20241201104921.GAZ0w_Mev3hhUdkHHr@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®