From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Shivansh Dhiman <shivansh.dhiman@amd.com>,
Nikunj A Dadhania <nikunj@amd.com>
Subject: Re: [PATCH 7.3.y 1/2] KVM: SVM: Add a vCPU-aware helper to get supported DEBUGCTL bits
Date: Thu, 12 Nov 2026 09:11:09 -0800 [thread overview]
Message-ID: <avXzLcD_56mvDYYz@google.com> (raw)
In-Reply-To: <20261111170439.3395604-1-sashal@kernel.org>
On Wed, Nov 11, 2026, Sasha Levin wrote:
> From: Shivansh Dhiman <shivansh.dhiman@amd.com>
>
> [ Upstream commit cd0e6f4d7cec11be97fe6476309719b23ab5accb ]
>
> Replace DEBUGCTL_RESERVED_BITS with a vCPU-aware helper that provides the
> set of supported bits so that KVM can handle bits that are conditionally
> supported based on the vCPU model, e.g. for features like Bus Lock Detect.
>
> No functional change intended.
>
> Signed-off-by: Shivansh Dhiman <shivansh.dhiman@amd.com>
> Reviewed-by: Nikunj A Dadhania <nikunj@amd.com>
> [sean: invert from reserved => supported, massage changelog]
> Link: https://patch.msgid.link/20260930193634.3415089-12-seanjc@google.com
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> Stable-dep-of: 053621535f01 ("KVM: nSVM: Check validity of vmcs01 save area copied from SMRAM on RSM")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
The superficial conflict could also be resolved manually, but I don't see any
harm in grabbing this refactor.
Acked-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2026-11-12 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 1:01 FAILED: patch "[PATCH] KVM: nSVM: Check validity of vmcs01 save area copied from SMRAM on RSM" failed to apply to 7.3-stable tree Sasha Levin
2026-11-11 17:04 ` [PATCH 7.3.y 1/2] KVM: SVM: Add a vCPU-aware helper to get supported DEBUGCTL bits Sasha Levin
2026-11-11 17:04 ` [PATCH 7.3.y 2/2] KVM: nSVM: Check validity of vmcs01 save area copied from SMRAM on RSM Sasha Levin
2026-11-12 17:11 ` Sean Christopherson
2026-11-12 17:11 ` Sean Christopherson [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=avXzLcD_56mvDYYz@google.com \
--to=seanjc@google.com \
--cc=nikunj@amd.com \
--cc=sashal@kernel.org \
--cc=shivansh.dhiman@amd.com \
--cc=stable@vger.kernel.org \
/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.