Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2117606imm; Thu, 27 Sep 2018 07:42:17 -0700 (PDT) X-Google-Smtp-Source: ACcGV62Ay+L1tMVP57ZtxyXdHDSw5+5kct8S1y5TF8T3lfOR8XtXDaFq/Mr3jcEwP2KZyZQG85Z1 X-Received: by 2002:a17:902:7d83:: with SMTP id a3-v6mr11595967plm.0.1538059337613; Thu, 27 Sep 2018 07:42:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538059337; cv=none; d=google.com; s=arc-20160816; b=gxwCB3xcXvAvHbRbofi0OrUAgGX8vp28hrTW/I5DKZT9eeDaC9y2NoxgSj8Bbr4wpp 8mUDajRzlXnFRPQNc95nfvPc4y///3gGEZZSJ9CVs5Sv2Ok5CCuJNjF689vT3B58Pxwl hHz4fO/REqMiS326WX7eQigF5Sb+DKqhAS15jl3xwhP9vdY23fkI9DJSGuKteXEOjKK5 O2wly0N5WAiBq0bvazO1neG+lYRTMs3WTqaCC6zeaY8OH2Y2VoJA1diJlhq4gQ4xPZLM OCbZF0qijuEtD0+cwzAim5kN0h1KE5Quk6ZF+EyBp59tNGv/Ldo0Hs+3K51u6JVC66S5 Bjsg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=rXNl+N0G+XX4stQMj1k5Xu0XZMnfZhjC4fVUxRJ7964=; b=FCTf6jhgo2ybroTIFv1TwAgUc2vE0c8dhEzY0pv4/CKnPiUTI2xIoLGg+llI04nF9K Ytt0jypqvZOtZG0WFGXlD9sDeGsY85HOkKnoMFHoY95cfN2iAvLL5AkHQ9Idj2d5IcGX OnSYptrUwZuoniIWhfBHESzMcV/H4TgigVQp930L2J72BAl9MmU2LgswfDMjUiDJC+w3 kGjDJtx0kqqPV+W2m7KurVG4sEhQk9SqOVpMusgQ2WrN974zDSE6qwBHkz9xnE7cqmcX bNdlWha2WqEHdVmCVzpHv1525lh5qGNjbEyyl25lAIod/6Qt2dpLDrc1fD+myCWi59r4 P9tg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k10-v6si2142387pgj.381.2018.09.27.07.42.01; Thu, 27 Sep 2018 07:42:17 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728046AbeI0U7w (ORCPT + 99 others); Thu, 27 Sep 2018 16:59:52 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:52146 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727076AbeI0U7w (ORCPT ); Thu, 27 Sep 2018 16:59:52 -0400 Received: from p5492e4c1.dip0.t-ipconnect.de ([84.146.228.193] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1g5XTd-0005NL-EC; Thu, 27 Sep 2018 16:41:13 +0200 Date: Thu, 27 Sep 2018 16:41:12 +0200 (CEST) From: Thomas Gleixner To: Peter Zijlstra cc: John Stultz , Andy Lutomirski , LKML , X86 ML , Matt Rickard , Stephen Boyd , Florian Weimer , "K. Y. Srinivasan" , Vitaly Kuznetsov , devel@linuxdriverproject.org, Linux Virtualization , Paolo Bonzini , Arnd Bergmann , Juergen Gross Subject: Re: [patch 09/11] x86/vdso: Simplify the invalid vclock case In-Reply-To: Message-ID: References: <20180914125006.349747096@linutronix.de> <20180914125118.909646643@linutronix.de> <20180918083055.GJ24106@hirez.programming.kicks-ass.net> <20180918124800.GL24106@hirez.programming.kicks-ass.net> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 18 Sep 2018, Thomas Gleixner wrote: > On Tue, 18 Sep 2018, Thomas Gleixner wrote: > > So if the TSC on CPU1 is slightly behind the TSC on CPU0 then now1 can be > > smaller than cycle_last. The TSC sync stuff does not catch the small delta > > for unknown raisins. I'll go and find that machine and test that again. > > Of course it does not trigger anymore. We accumulated code between the > point in timekeeping_advance() where the TSC is read and the update of the > VDSO data. > > I'll might have to get an 2.6ish kernel booted on that machine and try with > that again. /me shudders Actually it does happen, because the TSC is very slowly drifting apart due to SMI wreckage trying to hide itself. It just takes a very long time. Thanks, tglx