From: Sean Christopherson <seanjc@google.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Nikunj A Dadhania <nikunj@amd.com>,
pbonzini@redhat.com, kvm@vger.kernel.org,
santosh.shukla@amd.com, bp@alien8.de, ketanch@iitk.ac.in,
isaku.yamahata@intel.com
Subject: Re: [PATCH v2 3/4] KVM: SVM: Prevent writes to TSC MSR when Secure TSC is enabled
Date: Tue, 11 Feb 2025 14:37:16 -0800 [thread overview]
Message-ID: <Z6vRHK72H66v7TRq@google.com> (raw)
In-Reply-To: <8ec1bef9-829d-4370-47f6-c94e794cc5d5@amd.com>
On Mon, Feb 10, 2025, Tom Lendacky wrote:
> On 2/10/25 03:22, Nikunj A Dadhania wrote:
> > Disallow writes to MSR_IA32_TSC for Secure TSC enabled SNP guests, as such
> > writes are not expected. Log the error and return #GP to the guest.
>
> Re-word this to make it a bit clearer about why this is needed. It is
> expected that the guest won't write to MSR_IA32_TSC or, if it does, it
> will ignore any writes to it and not exit to the HV. So this is catching
> the case where that behavior is not occurring.
Unless it's architectural impossible for KVM to modify MSR_IA32_TSC, I don't see
any reason for KVM to care. If the guest wants to modify TSC, that's the guest's
prerogative.
If KVM _can't_ honor the write, then that's something else entirely, and the
changelog should pretty much write itself.
next prev parent reply other threads:[~2025-02-11 22:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 9:22 [PATCH v2 0/4] Enable Secure TSC for SEV-SNP Nikunj A Dadhania
2025-02-10 9:22 ` [PATCH v2 1/4] x86/cpufeatures: Add SNP Secure TSC Nikunj A Dadhania
2025-02-11 14:30 ` Borislav Petkov
2025-02-10 9:22 ` [PATCH v2 2/4] KVM: SVM: Add GUEST_TSC_FREQ MSR for Secure TSC enabled guests Nikunj A Dadhania
2025-02-10 9:22 ` [PATCH v2 3/4] KVM: SVM: Prevent writes to TSC MSR when Secure TSC is enabled Nikunj A Dadhania
2025-02-10 20:21 ` Tom Lendacky
2025-02-11 8:24 ` Nikunj A Dadhania
2025-02-11 14:03 ` Tom Lendacky
2025-02-11 14:42 ` Tom Lendacky
2025-02-12 4:26 ` Nikunj A Dadhania
2025-02-11 22:37 ` Sean Christopherson [this message]
2025-02-12 8:37 ` Nikunj A Dadhania
2025-02-12 14:04 ` Sean Christopherson
2025-02-14 5:14 ` Nikunj A. Dadhania
2025-02-14 5:37 ` subscribe list archives
2025-02-10 9:22 ` [PATCH v2 4/4] KVM: SVM: Enable Secure TSC for SNP guests Nikunj A Dadhania
2025-02-10 20:41 ` Tom Lendacky
2025-02-11 8:11 ` Nikunj A Dadhania
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=Z6vRHK72H66v7TRq@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=isaku.yamahata@intel.com \
--cc=ketanch@iitk.ac.in \
--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 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.