From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [RFC v2 kernel] backport patch to fix TSC scaling for SVM
Date: Fri, 21 Oct 2022 17:24:55 +0200 [thread overview]
Message-ID: <5f763876-88c8-97a0-0a3c-261baf381393@proxmox.com> (raw)
In-Reply-To: <20220902124409.42944-1-f.ebner@proxmox.com>
Am 02/09/2022 um 14:44 schrieb Fiona Ebner:
> The following issue reported on the community forum [0] is likely
> fixed by this.
>
> In my case, loading a VM snapshot that originally was taken on an
> Intel CPU on my AMD-based host often caused problems in other VMs. In
> particular, it often led to CPU stalls, and sometimes clock jumps far
> into the future. With this backport applied, everything seems to run
> smoothly even after loading the "bad" snapshot 10 times.
>
> The backport from upstream commit 11d39e8cc43e ("KVM: SVM: fix tsc
> scaling cache logic consisted of dropping the parts for nested TSC
> scaling, which is not yet present in our kernel, renaming the constant
> for the default ratio, and some context changes.
>
> [0] https://forum.proxmox.com/threads/112756/
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Changes from v1:
> * Alternative approach backporting the fix of the bad commit.
>
> ...-KVM-SVM-fix-tsc-scaling-cache-logic.patch | 113 ++++++++++++++++++
> 1 file changed, 113 insertions(+)
> create mode 100644 patches/kernel/0032-KVM-SVM-fix-tsc-scaling-cache-logic.patch
>
>
applied, thanks!
prev parent reply other threads:[~2022-10-21 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 12:44 [pve-devel] " Fiona Ebner
2022-10-21 8:02 ` Fiona Ebner
2022-10-21 15:24 ` 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=5f763876-88c8-97a0-0a3c-261baf381393@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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