From: Sean Christopherson <seanjc@google.com>
To: Daniil Tatianin <d-tatianin@yandex-team.ru>
Cc: stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Sasha Levin <sashal@kernel.org>,
"Xin Li (Intel)" <xin@zytor.com>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
"Ahmed S. Darwish" <darwi@linutronix.de>,
Nikunj A Dadhania <nikunj@amd.com>
Subject: Re: [PATCH 6.6.y 5/5] x86/bugs: KVM: Add support for SRSO_MSR_FIX
Date: Tue, 28 Apr 2026 10:23:22 -0700 [thread overview]
Message-ID: <afDtCg-8DyaPb-0s@google.com> (raw)
In-Reply-To: <20260428120545.1970058-6-d-tatianin@yandex-team.ru>
On Tue, Apr 28, 2026, Daniil Tatianin wrote:
> [ Upstream commit 8442df2b49ed9bcd67833ad4f091d15ac91efd00 ]
This shouldn't be backported without also grabbing upstream commit e3417ab75ab2
("KVM: SVM: Set/clear SRSO's BP_SPEC_REDUCE on 0 <=> 1 VM count transitions"),
otherwise non-KVM workloads will get hit with performance regressions without
any benefit (to them).
next prev parent reply other threads:[~2026-04-28 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 12:05 [PATCH 6.6.y 0/5] SRSO handling for Zen5 CPUs Daniil Tatianin
2026-04-28 12:05 ` [PATCH 6.6.y 1/5] x86/bugs: Add SRSO_USER_KERNEL_NO support Daniil Tatianin
2026-04-28 12:05 ` [PATCH 6.6.y 2/5] x86/srso: Print actual mitigation if requested mitigation isn't possible Daniil Tatianin
2026-04-28 12:05 ` [PATCH 6.6.y 3/5] x86/srso: Remove 'pred_cmd' label Daniil Tatianin
2026-04-28 12:05 ` [PATCH 6.6.y 4/5] x86/bugs: Fix handling when SRSO mitigation is disabled Daniil Tatianin
2026-04-28 12:05 ` [PATCH 6.6.y 5/5] x86/bugs: KVM: Add support for SRSO_MSR_FIX Daniil Tatianin
2026-04-28 17:23 ` Sean Christopherson [this message]
2026-04-28 20:47 ` Daniil Tatianin
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=afDtCg-8DyaPb-0s@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=d-tatianin@yandex-team.ru \
--cc=daniel.sneddon@linux.intel.com \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=xin@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.