Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp5550567imm; Tue, 19 Jun 2018 12:14:36 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKvJkYngXYE6BSUQLoYX4IVT5jWzhv0dglMWk0HE4qUG2d8SG7Ql0a0/vmz3Eo/WNbCPLMp X-Received: by 2002:a62:1411:: with SMTP id 17-v6mr19465475pfu.3.1529435676805; Tue, 19 Jun 2018 12:14:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529435676; cv=none; d=google.com; s=arc-20160816; b=CANq0au87OXACyTigRkntt1oPHrEpjRFs/AFeIVv16XYKhC0Ab6IVpOW/z6gS2D49J I+p0fyYk1dMFtSnYmsJqMKEJRMa1shzwD6rvBTPXwIpq+smDkbtC0jEZUIPwBQbqsi39 9MK7WCKZ4rXhHbojYawaMQAxOm8mBkXxucEzIaGsMvThien6XDpzuEmLKF4ZqUBqy2ky Xv4tVye0gzbVPUTSe3Y8fxX4NlBN8cxMtuAq+mzTGGgIbvkDGjl3Tvg29RF+45mlqkoh saR87pTT30gJptksLkiMAi7lSiIRIp//9VgoR1Byj2dsefujFK+++aSXN3LmNj/GsaK1 ztOQ== 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 :arc-authentication-results; bh=ztRXHo7KpynZvfKJ/0ON8mKQEvm7D2hzOY+5+LLYc/c=; b=SwYO71OTMuXc8a3xPLAxvV/HSx81jK5t32GL4cXzr03dj/08RH8o8pVbeZo2MAz3g1 N9qzKsYgqQuGFlOKXLEtLSVipB74XCnIEMwqaRDDQlJqKw/4FNBuke159/RXhz34WOSx jdNlymQSWRCBeTd8mTKuVR/zkfGAGVmRmZfQtiUd/911IjHG2ZjJIhUu1hRLL+CdE6a3 yGfozwEo4spYf7PG3Kw3SqwCUr05jxZU658GR229hvajqI8vKPbTcAuHwVKnR33RG/yt HWsD5xdVrHW8Q7nWsz4OBZrbWOI3AuibzvuiAXHZAUxMgHhJX3ffJ/a/mdhJi4EiX1NV hurQ== 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 d18-v6si325924pgv.248.2018.06.19.12.14.13; Tue, 19 Jun 2018 12:14:36 -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 S967157AbeFSTNH (ORCPT + 99 others); Tue, 19 Jun 2018 15:13:07 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:58019 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966747AbeFSTNG (ORCPT ); Tue, 19 Jun 2018 15:13:06 -0400 Received: from p4fea482e.dip0.t-ipconnect.de ([79.234.72.46] helo=nanos.glx-home) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fVM3b-0002eG-I0; Tue, 19 Jun 2018 21:12:47 +0200 Date: Tue, 19 Jun 2018 21:12:45 +0200 (CEST) From: Thomas Gleixner To: Peter Zijlstra cc: Pavel Tatashin , steven.sistare@oracle.com, daniel.m.jordan@oracle.com, linux@armlinux.org.uk, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, john.stultz@linaro.org, sboyd@codeaurora.org, x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com, douly.fnst@cn.fujitsu.com, prarit@redhat.com, feng.tang@intel.com, pmladek@suse.com, gnomes@lxorguk.ukuu.org.uk Subject: Re: [PATCH v10 1/7] x86/tsc: remove tsc_disabled flag In-Reply-To: <20180619184654.GG2494@hirez.programming.kicks-ass.net> Message-ID: References: <20180615174204.30581-1-pasha.tatashin@oracle.com> <20180615174204.30581-2-pasha.tatashin@oracle.com> <20180619184654.GG2494@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, 19 Jun 2018, Peter Zijlstra wrote: > On Tue, Jun 19, 2018 at 07:32:49PM +0200, Thomas Gleixner wrote: > > On Fri, 15 Jun 2018, Pavel Tatashin wrote: > > > > > tsc_disabled is set when notsc is passed as kernel parameter. The reason we > > > have notsc is to avoid timing problems on multi-socket systems. We already > > > have a mechanism, however, to detect and resolve these issues by invoking > > > tsc unstable path. Thus, make notsc to behave the same as tsc=unstable. > > > > notsc also excludes TSC from being used at all > > It does not; there is TSC usage even if you boot with notsc on. See how > it does not clear X86_FEATURE_TSC for instance. Well, kinda. There is some stuff in the apic calibration which uses TSC independent of tsc_disabled, but that's about it. Thanks, tglx