From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-kernel] cherry-pick fix for new amd64 ucode
Date: Tue, 26 Sep 2023 11:38:21 +0200 [thread overview]
Message-ID: <0e8f90c5-f244-4b5e-99a1-22c60f18e933@proxmox.com> (raw)
In-Reply-To: <20230925172335.197562-1-s.ivanov@proxmox.com>
Am 25/09/2023 um 19:23 schrieb Stoiko Ivanov:
> The latest amd64-microcode package in sid [0] (which probably will
> eventually make it to bookworm-security) has a change that requires
> the added patch to work properly.
>
> The changelog-entry refers to stable k.o branches only - but a quick
> look through the linux-firmware.git log identifies:
> `f2eb058afc57348cde66852272d6bf11da1eef8f` as relevant commit, which
> refers (as NOTE in the patch) to:
> a32b0f0db3f3 ("x86/microcode/AMD: Load late on both threads too")
> which applies cleanly (although I cherry-picked the patch from the
> 6.1.y stable branch to have the original commit in the commit message).
>
> quickly tested compiling and booting the result in a VM (however w/o
> a fitting CPU (Epyc Genoa or Bergamo) it should cause a change)
>
> reported in our Enterprise Support as potential culprit for one
> thread from 128 being reported as offline in `lscpu`
>
> [0] https://metadata.ftp-master.debian.org/changelogs//non-free-firmware/a/amd64-microcode/amd64-microcode_3.20230808.1.1_changelog
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> ...de-AMD-Load-late-on-both-threads-too.patch | 32 +++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 patches/kernel/0018-x86-microcode-AMD-Load-late-on-both-threads-too.patch
>
>
applied, thanks!
prev parent reply other threads:[~2023-09-26 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 17:23 [pve-devel] " Stoiko Ivanov
2023-09-26 9:38 ` Thomas Lamprecht [this message]
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=0e8f90c5-f244-4b5e-99a1-22c60f18e933@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/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