public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied-series: [PATCH-SERIES kernel] backport fix for kvm performance regression with Intel Emerald Rapids
Date: Mon, 20 Jan 2025 13:52:56 +0100	[thread overview]
Message-ID: <d8dd5ded-163a-416c-ab76-a6189ea825fb@proxmox.com> (raw)
In-Reply-To: <20241219142947.1447728-1-f.ebner@proxmox.com>

Am 19.12.24 um 15:29 schrieb Fiona Ebner:
> Stumbled across this in the news [0].
> 
> Built, installed on a (CPU type 'host') VM and started a nested VM for
> both 6.8 and 6.11 as a smoke test. Note I have an AMD TR 7960X, but
> AFIACT, the patch affects a general code path not specific to Intel
> CPUs.
> 
> [0]: https://www.phoronix.com/news/Linux-6.13-rc3-Released
> 
> 
> Fiona Ebner (2):
>   patches: kernel: switch to using full index for patch files
>   backport fix for kvm performance regression with Intel Emerald Rapids
> 
>  ...-accept-an-alternate-timestamp-strin.patch |   2 +-
>  ...d-Debian-wireless-regdb-certificates.patch |   2 +-
>  ...idge-keep-MAC-of-first-assigned-port.patch |   2 +-
>  ...ides-for-missing-ACS-capabilities-4..patch |   4 +-
>  ...-default-dynamic-halt-polling-growth.patch |   2 +-
>  ...de-unregister_netdevice-refcount-lea.patch |   2 +-
>  ...fortify-Do-not-cast-to-unsigned-char.patch |   2 +-
>  ...sk-out-PKRU-bit-in-xfeatures-if-vCPU.patch |   6 +-
>  ...allow-pass-through-on-broken-hardwar.patch |   2 +-
>  ...-Advertise-support-for-flush-by-ASID.patch |   2 +-
>  ...rove-userspace-warnings-for-missing-.patch |   2 +-
>  ...pect-msg_namelen-0-for-recvmsg-calls.patch |   2 +-
>  ...ix-pagecache-leak-when-do-writepages.patch |   2 +-
>  ...pu-pm-Don-t-use-OD-table-on-Arcturus.patch |   2 +-
>  ...UCE-iommu-intel-disable-DMAR-for-SKL.patch |   2 +-
>  ...t-EOPNOTSUPP-for-IOCB_NOWAIT-like-EA.patch |   2 +-
>  ...et-subreq-iov-iter-before-tail-clean.patch |   2 +-
>  ...r-virtualized-VMLOAD-VMSAVE-on-Zen4-.patch |   2 +-
>  ...UID.0xD-XSTATE-offsets-sizes-during-.patch | 165 ++++++++++++++++++
>  19 files changed, 186 insertions(+), 21 deletions(-)
>  create mode 100644 patches/kernel/0019-KVM-x86-Cache-CPUID.0xD-XSTATE-offsets-sizes-during-.patch
> 

For the record, this series was already applied in December by Thomas.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2025-01-20 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 14:29 [pve-devel] " Fiona Ebner
2024-12-19 14:29 ` [pve-devel] [PATCH master kernel 1/4] patches: kernel: switch to using full index for patch files Fiona Ebner
2024-12-19 14:44   ` Fiona Ebner
2024-12-19 14:29 ` [pve-devel] [PATCH master kernel 2/4] backport fix for kvm performance regression with Intel Emerald Rapids Fiona Ebner
2024-12-19 14:29 ` [pve-devel] [PATCH bookworm-6.8 kernel 3/4] patches: kernel: switch to using full index for patch files Fiona Ebner
2024-12-19 14:29 ` [pve-devel] [PATCH bookworm-6.8 kernel 4/4] backport fix for kvm performance regression with Intel Emerald Rapids Fiona Ebner
2025-01-20 12:52 ` Fiona Ebner [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=d8dd5ded-163a-416c-ab76-a6189ea825fb@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal