From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755073AbdCWK5L (ORCPT ); Thu, 23 Mar 2017 06:57:11 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:58806 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752815AbdCWK5J (ORCPT ); Thu, 23 Mar 2017 06:57:09 -0400 Date: Thu, 23 Mar 2017 11:56:17 +0100 (CET) From: Thomas Gleixner To: Pasha Tatashin cc: Peter Zijlstra , x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com Subject: Re: [v1 0/9] Early boot time stamps for x86 In-Reply-To: Message-ID: References: <1490214265-899964-1-git-send-email-pasha.tatashin@oracle.com> <20170322202807.y34mrortprg5pi43@hirez.programming.kicks-ass.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 22 Mar 2017, Pasha Tatashin wrote: > Yes, I am certain it is 0 or near 0 on reset on this machine. Because, I Emphasis on "this machine' It's not guaranteed especially not on reboot and not with creative BIOSes fiddling with the TSC_ADJUST value. - It CANNOT be used to measure BIOS boot time reliably - If BIOS wreckaged TSC_ADJUST, then your whole time stamping goes out the window once the kernel sanitized it. See other mail. Thanks, tglx