From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Nikunj A. Dadhania" <nikunj@amd.com>
Cc: Xiaoyao Li <xiaoyao.li@intel.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
kvm@vger.kernel.org, pbonzini@redhat.com,
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, Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH 0/2] KVM: kvm-coco-queue: Support protected TSC
Date: Tue, 29 Oct 2024 10:44:59 -0300 [thread overview]
Message-ID: <ZyDm25/oSBfuUpqj@tpad> (raw)
In-Reply-To: <714ab7a2-69fa-b08d-deae-6eb91ecba95b@amd.com>
On Tue, Oct 29, 2024 at 09:34:58AM +0530, Nikunj A. Dadhania wrote:
> Hello Marcelo
>
> On 10/28/2024 10:12 PM, Marcelo Tosatti wrote:
> > On Sun, Oct 27, 2024 at 10:06:17PM +0800, Xiaoyao Li wrote:
> >> On 10/26/2024 12:24 AM, Marcelo Tosatti wrote:
> >>> On Mon, Oct 14, 2024 at 08:17:19PM +0530, Nikunj A. Dadhania wrote:
> >>>> Hi Isaku,
> >>>>
> >>>> On 10/12/2024 1:25 PM, Isaku Yamahata wrote:
> >>>>> Choose the first one. With this patch series, SEV-SNP secure TSC can be
> >>>>> supported.
> >>>>
> >>>> I am not sure how will this help SNP Secure TSC, as the GUEST_TSC_OFFSET and
> >>>> GUEST_TSC_SCALE are only available to the guest.
> >>>
> >>> Nikunj,
> >>>
> >>> FYI:
> >>>
> >>> SEV-SNP processors (at least the one below) do not seem affected by this problem.
> >>
> >> Did you apply Secure TSC patches of (guest kernel, KVM and QEMU) manualy?
> >> because none of them are merged.
> >
> > Yes. cyclictest latency, on a system configured with tuned
> > realtime-virtual-host/realtime-virtual-guest tuned profiles,
> > goes from 30us to 50us.
>
> Would you be ok if I include your Tested-by in the next version of my Secure TSC patches?
>
> https://lore.kernel.org/lkml/20241028053431.3439593-1-nikunj@amd.com/
Please don't, haven't tested specifically the patches above.
> >> Otherwise, I think SNP guest is still using
> >> KVM emulated TSC.
> >
> > Not in the case the test was made.
> >
>
> Regards,
> Nikunj
>
>
next prev parent reply other threads:[~2024-10-29 13:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 7:55 [PATCH 0/2] KVM: kvm-coco-queue: Support protected TSC 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 [this message]
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
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=ZyDm25/oSBfuUpqj@tpad \
--to=mtosatti@redhat.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=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=xiaoyao.li@intel.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