From: Sean Christopherson <seanjc@google.com>
To: Nikunj A Dadhania <nikunj@amd.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org,
thomas.lendacky@amd.com, santosh.shukla@amd.com
Subject: Re: [PATCH] KVM: SVM: Add module parameter to control SEV-SNP Secure TSC feature
Date: Wed, 29 Oct 2025 06:58:25 -0700 [thread overview]
Message-ID: <aQIdgeaeQ0wzGUz7@google.com> (raw)
In-Reply-To: <20251029055753.5742-1-nikunj@amd.com>
On Wed, Oct 29, 2025, Nikunj A Dadhania wrote:
> Add a module parameter secure_tsc to allow control of the SEV-SNP Secure
> TSC feature at module load time, providing administrators with the ability
> to disable Secure TSC support even when the hardware and kernel support it.
Why?
next prev parent reply other threads:[~2025-10-29 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 5:57 [PATCH] KVM: SVM: Add module parameter to control SEV-SNP Secure TSC feature Nikunj A Dadhania
2025-10-29 13:18 ` Tom Lendacky
2025-10-29 13:58 ` Sean Christopherson [this message]
2025-10-29 15:38 ` Tom Lendacky
2025-10-29 16:52 ` 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=aQIdgeaeQ0wzGUz7@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=santosh.shukla@amd.com \
--cc=thomas.lendacky@amd.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