linux-kernel - Re: [PATCH] x86/acrn: Set X86_FEATURE_TSC_KNOWN

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] [day] [month] [year] [list]

Date:   Wed, 26 Oct 2022 11:32:27 +0800
From:   Fei Li <fei1.li@...el.com>
To:     Peter Zijlstra <peterz@...radead.org>
CC:     <linux-kernel@...r.kernel.org>, <x86@...nel.org>,
        <dave.hansen@...el.com>, <gregkh@...uxfoundation.org>,
        <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
        <dave.hansen@...ux.intel.com>, <hpa@...or.com>,
        <Yu1.Wang@...el.com>, <conghui.chen@...el.com>,
        <fengwei.yin@...el.com>
Subject: Re: [PATCH] x86/acrn: Set X86_FEATURE_TSC_KNOWN_FREQ

On 2022-10-25 at 15:22:58 +0200, Peter Zijlstra wrote:
> On Tue, Oct 25, 2022 at 04:41:47PM +0800, Fei Li wrote:
> > Avoiding recalibration by setting X86_FEATURE_TSC_KNOWN_FREQ.
> > This patch also removes `inline` for acrn_get_tsc_khz() since
> > it doesn't make sense.
> 
Hi Peter

Thanks for your comments.

> Can we have a few words on how this is supposed to work at all?

If the TSC frequency is known from the acrn_get_tsc_khz(),
the TSC frequency does not need to be recalibrated.

We can avoid recalibration by setting X86_FEATURE_TSC_KNOWN_FREQ.
> 
> Supposedly the HV is providing host rate through this ACRN CPUID leaf?
ACRN would provide the calibrated TSC frequency, not just the
host rate through this CPUID leaf.

> How does it deal with systems where TSC isn't known stable?
>