From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Daniil Tatianin <d-tatianin@yandex-team.ru>,
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>,
"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>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH 6.6.y v1 0/6] SRSO handling for Zen5 CPUs
Date: Wed, 29 Apr 2026 13:50:36 -0400 [thread overview]
Message-ID: <20260429171550.srso-zen5-6.6.y@kernel.org> (raw)
In-Reply-To: <20260428214610.2138600-1-d-tatianin@yandex-team.ru>
On Wed, Apr 29, 2026 at 12:46:04AM +0300, Daniil Tatianin wrote:
> This series backports a few SRSO handling features for Zen5 CPUs from the
> mainline kernel. The only important ones are
> "x86/bugs: KVM: Add support for SRSO_MSR_FIX" and
> "x86/bugs: Add SRSO_USER_KERNEL_NO support". The rest are added to avoid
> conflicts when applying the aforementioned patches.
>
> Changes since v0:
> - Add e3417ab75ab2 ("KVM: SVM: Set/clear SRSO's BP_SPEC_REDUCE on 0 <=> 1 VM count transitions")
> to fix a performance regression introduced by 8442df2b49ed ("x86/bugs: KVM: Add support for SRSO_MSR_FIX")
> (Suggested by Sean Christopherson)
Sean, are you OK with this 6.6.y backport as it stands?
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-04-29 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 21:46 [PATCH 6.6.y v1 0/6] SRSO handling for Zen5 CPUs Daniil Tatianin
2026-04-28 21:46 ` [PATCH 6.6.y v1 1/6] x86/bugs: Add SRSO_USER_KERNEL_NO support Daniil Tatianin
2026-04-28 21:46 ` [PATCH 6.6.y v1 2/6] x86/srso: Print actual mitigation if requested mitigation isn't possible Daniil Tatianin
2026-04-28 21:46 ` [PATCH 6.6.y v1 3/6] x86/srso: Remove 'pred_cmd' label Daniil Tatianin
2026-04-28 21:46 ` [PATCH 6.6.y v1 4/6] x86/bugs: Fix handling when SRSO mitigation is disabled Daniil Tatianin
2026-04-28 21:46 ` [PATCH 6.6.y v1 5/6] x86/bugs: KVM: Add support for SRSO_MSR_FIX Daniil Tatianin
2026-04-30 17:47 ` Sean Christopherson
2026-04-28 21:46 ` [PATCH 6.6.y v1 6/6] KVM: SVM: Set/clear SRSO's BP_SPEC_REDUCE on 0 <=> 1 VM count transitions Daniil Tatianin
2026-04-30 17:47 ` Sean Christopherson
2026-04-29 17:50 ` Sasha Levin [this message]
2026-04-30 17:49 ` [PATCH 6.6.y v1 0/6] SRSO handling for Zen5 CPUs Sean Christopherson
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=20260429171550.srso-zen5-6.6.y@kernel.org \
--to=sashal@kernel.org \
--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=seanjc@google.com \
--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.