Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp41338imm; Tue, 19 Jun 2018 13:59:06 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKvFYaGNEC+xFDWcHu3mKVi6dA9MNHOZnAVstMmIAl3oJm1jn6g3mlFCt50RTrTDcljIqcJ X-Received: by 2002:a63:ac11:: with SMTP id v17-v6mr16431012pge.274.1529441946249; Tue, 19 Jun 2018 13:59:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529441946; cv=none; d=google.com; s=arc-20160816; b=CYXWE6nCjoNdwoFR+slhhcpWT9JyMDPTJxfbyeAxmoX0B0QIh5ctwxY45RzNWwHSzu H/aqBD2yW+CcfleSTgYWwzwOhEqAGMc8tN6UVIBtkR4JrMkNpJKwpKHGsw1pp00XkANS 47uwqtbHOoDQ2HluQxo5js/Wlfh46iJCnlMPIxhJRBSVhnEoImKIVZN+Nb3IcClY1XF9 1hLsGKd29FF6BgiDp7aNJ9CLDDx5rr/Phd7GNSXPIbajksI7Ju+3P7b9VvMxZPPi8584 /urTNQLsOv2VEYfwWu2sYxnFisBvoPpGDeOoXY3tH7fDAIIXWUW84HBEKCiwjTA/BJMa zsVg== 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=N23ztWgcC3+iVdBp+Oes5NQd/yIhCQAAgAUYSK92jpk=; b=O2quvreMYTiyhTlE92qlPeqFAw1xjsUF3PHR8hIRkWYl3prUZatUk5hFxGaLHWM1YM ArOkKf/zvILacZriyvO3bWU7me9feaQhR960dVsheuMRUMDjytZeREvAjRdH4qRDx5k3 /SzpY6o4M+dbzCBokqdtUDRzWE1dCLwfxMyXsuRvjiX4icqVaiV2g3SfH/b13gEZeRTW XLHSgVzLHfMkU3b2GWCrmQhgfsMu+jZPlCTuhMzDy+jQJ6IuVDG4vGrPSyIrthkBmwoP kWAtgtbcJI/3tHt//WeNh0+UcoybclGAk5L0o8ftQI8OvnRb4kGX/ew67V5wqf5gr6zi WvSA== 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 b83-v6si617034pfk.342.2018.06.19.13.58.52; Tue, 19 Jun 2018 13:59:06 -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 S1030259AbeFSU6O (ORCPT + 99 others); Tue, 19 Jun 2018 16:58:14 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:58271 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755470AbeFSU6N (ORCPT ); Tue, 19 Jun 2018 16:58:13 -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 1fVNh2-0003ow-Nz; Tue, 19 Jun 2018 22:57:36 +0200 Date: Tue, 19 Jun 2018 22:57:35 +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: <20180619200115.GH2494@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> <20180619200115.GH2494@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 09:12:45PM +0200, Thomas Gleixner wrote: > > On Tue, 19 Jun 2018, Peter Zijlstra wrote: > > > 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. > > Still, that precludes booting on hardware without TSC, so what's the > point of having notsc? I'm all for killing the thing. I'm not arguing against removing it. I just refuse to accept changelogs which suggest that there is no functional change. Thanks, tglx