linux-kernel - Re: [PATCH v2 09/11] x86/kvmclock: Use Secure TSC as clock if available

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7f07f8ea-cc26-7655-00de-4ab21bc4b0e7@amd.com>
Date:   Wed, 5 Apr 2023 13:46:50 +0530
From:   "Nikunj A. Dadhania" <nikunj@....com>
To:     Tom Lendacky <thomas.lendacky@....com>,
        linux-kernel@...r.kernel.org, x86@...nel.org
Cc:     bp@...en8.de, dionnaglaze@...gle.com, pgonda@...gle.com,
        seanjc@...gle.com, pbonzini@...hat.com, michael.roth@....com,
        ketanch@...k.ac.in
Subject: Re: [PATCH v2 09/11] x86/kvmclock: Use Secure TSC as clock if
 available

On 4/4/2023 3:15 AM, Tom Lendacky wrote:
> On 3/26/23 09:46, Nikunj A Dadhania wrote:
>> For AMD SNP guests having Secure TSC enabled, use Secure TSC based
>> clocksource instead of kvmclock.
> 
> This patch only results in skipping the initialization of KVM clock, it doesn't cause Secure TSC to be used as the clocksource.
> 

Will update the commit message and reorder with 10/11. After making TSC reliable and skipping kvmclock, secure tsc is used as clocksource.

Regards
Nikunj