From: "Nikunj A. Dadhania" <nikunj@amd.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
chao.gao@intel.com, rick.p.edgecombe@intel.com,
yan.y.zhao@intel.com, linux-kernel@vger.kernel.org,
isaku.yamahata@gmail.com, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 0/2] KVM: kvm-coco-queue: Support protected TSC
Date: Wed, 12 Mar 2025 18:37:53 +0530 [thread overview]
Message-ID: <9f857e72-7992-4c37-af51-bea059092c2a@amd.com> (raw)
In-Reply-To: <c6cea2d0-80b5-4d05-84a7-0dc25c219d1d@redhat.com>
On 3/12/2025 5:52 PM, Paolo Bonzini wrote:
> On 10/12/24 09:55, Isaku Yamahata wrote:
>> The current x86 KVM implementation conflicts with protected TSC because the
>> VMM can't change the TSC offset/multiplier. Disable or ignore the KVM
>> logic to change/adjust the TSC offset/multiplier somehow.
>>
>> Because KVM emulates the TSC timer or the TSC deadline timer with the TSC
>> offset/multiplier, the TSC timer interrupts are injected to the guest at the
>> wrong time if the KVM TSC offset is different from what the TDX module
>> determined.
>>
>> Originally the issue was found by cyclic test of rt-test [1] as the latency in
>> TDX case is worse than VMX value + TDX SEAMCALL overhead. It turned out that
>> the KVM TSC offset is different from what the TDX module determines.
>>
>> The solution is to keep the KVM TSC offset/multiplier the same as the value of
>> the TDX module somehow. [...] Ignore (or don't call related functions) the
>> request to change the TSC offset/multiplier.
>>
>> [...] With this patch series, SEV-SNP secure TSC can be supported.
>
> Thanks, I've squashed these changes (apart from setting
> vcpu->arch.guest_tsc_protected) into the corresponding patches in
> kvm-coco-queue. Just one small change is needed in patch 2, to
> which I will reply.
>
> For SEV-SNP, all that's necessary on top should be
>
> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
> index d92e97baea0f..beddeed90ff0 100644
> --- a/arch/x86/kvm/svm/sev.c
> +++ b/arch/x86/kvm/svm/sev.c
> @@ -2481,6 +2481,9 @@ static int snp_launch_update_vmsa(struct kvm *kvm, struct kvm_sev_cmd *argp)
> }
>
> svm->vcpu.arch.guest_state_protected = true;
> + if (snp_secure_tsc_enabled(kvm))
> + svm->vcpu.arch.guest_tsc_protected = true;
> +
> /*
> * SEV-ES (and thus SNP) guest mandates LBR Virtualization to
> * be _always_ ON. Enable it only after setting
>
> For the sake of testing, I applied the latest SEV-SNP host patches
> from https://github.com/AMDESE/linux-kvm/commits/sectsc-host-latest
> to kvm-coco-queue as well, plus the above hunk; Nikunj can integrate
> it in the next revision of
> https://lore.kernel.org/kvm/20250310064347.13986-1-nikunj@amd.com/T/.
Sure Paolo, I will add the above changes in my next revision.
Should I rebase the Secure TSC host patches on top of kvm-coco-queue ?
Regards
Nikunj
prev parent reply other threads:[~2025-03-12 13:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 7:55 Isaku Yamahata
2024-10-12 7:55 ` [PATCH 1/2] KVM: x86: Push down setting vcpu.arch.user_set_tsc Isaku Yamahata
2024-10-12 7:55 ` [PATCH 2/2] KVM: x86: Don't allow tsc_offset, tsc_scaling_ratio to change Isaku Yamahata
2024-10-14 15:48 ` Edgecombe, Rick P
2024-11-21 23:50 ` Isaku Yamahata
2025-03-12 12:24 ` Paolo Bonzini
2025-03-14 0:39 ` Isaku Yamahata
2024-10-14 14:47 ` [PATCH 0/2] KVM: kvm-coco-queue: Support protected TSC Nikunj A. Dadhania
2024-10-25 16:24 ` Marcelo Tosatti
2024-10-27 14:06 ` Xiaoyao Li
2024-10-28 16:42 ` Marcelo Tosatti
2024-10-29 4:04 ` Nikunj A. Dadhania
2024-10-29 13:44 ` Marcelo Tosatti
2024-10-28 12:48 ` Nikunj A. Dadhania
2024-11-21 23:32 ` Isaku Yamahata
2025-03-12 1:13 ` Marcelo Tosatti
2025-03-14 0:43 ` Isaku Yamahata
2025-03-12 12:22 ` Paolo Bonzini
2025-03-12 13:07 ` Nikunj A. Dadhania [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=9f857e72-7992-4c37-af51-bea059092c2a@amd.com \
--to=nikunj@amd.com \
--cc=chao.gao@intel.com \
--cc=isaku.yamahata@gmail.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=yan.y.zhao@intel.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
all inboxes | Powered by JetHome®