[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <755ca898eab309445e461ee9f542ba7a4057d36c.camel@intel.com>
Date: Wed, 20 Aug 2025 11:25:22 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "pbonzini@...hat.com" <pbonzini@...hat.com>, "seanjc@...gle.com"
<seanjc@...gle.com>, "nikunj@....com" <nikunj@....com>
CC: "thomas.lendacky@....com" <thomas.lendacky@....com>, "kvm@...r.kernel.org"
<kvm@...r.kernel.org>, "vaishali.thakkar@...e.com"
<vaishali.thakkar@...e.com>, "Ketan.Chaturvedi@....com"
<Ketan.Chaturvedi@....com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "michael.roth@....com"
<michael.roth@....com>, "bp@...en8.de" <bp@...en8.de>
Subject: Re: [PATCH v11 0/8] KVM: SVM: Enable Secure TSC for SEV-SNP
On Wed, 2025-08-20 at 14:18 +0530, Nikunj A. Dadhania wrote:
> > - Continue on with snp_launch_start() if default_tsc_khz is '0'. AFAICT,
> > continuing on doesn't put the host at (any moer) risk. [Kai]
>
> If I hack default_tsc_khz as '0', SNP guest kernel with SecureTSC spits out
> couple of warnings and finally panics:
>
It's a surprise that the SEV_CMD_SNP_LAUNCH_START didn't fail in such
configuration. :-)
Powered by blists - more mailing lists