Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Florian Weimer <fw@deneb.enyo.de>
To:     Da Shi Cao <dscao999@gmail.com>
Cc:     linux-kernel@vger.kernel.org, linux-x86_64@vger.kernel.org
Subject: Re: [BUG]Uncalibrated TSC is not accurate enough as a time keeper
References: <CAG3POBnGPabdLQ2wvJc9HTKeHszf+RytV6t+hPyh0k=hjGd+8g@mail.gmail.com>
Date:   Thu, 27 Dec 2018 18:35:13 +0100
In-Reply-To: <CAG3POBnGPabdLQ2wvJc9HTKeHszf+RytV6t+hPyh0k=hjGd+8g@mail.gmail.com>
        (Da Shi Cao's message of "Sun, 23 Dec 2018 14:56:01 +0800")
Message-ID: <874layvpny.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

* Da Shi Cao:

> The cpu_khz and tsc_khz are now read directly by the cpuid
> instruction, and they are deemed to be very accurate. But this is not
> the case in our situation. The OS time lags behind about 8 seconds per
> hour. The CPU information is as follows:

Is virtualization involved?  Do you use a vendor kernel?

Note that <linux-x86_64@vger.kernel.org> is more or less dead, and
your message to linux-kernel might get lost in the flood.