Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1978806imm; Sat, 23 Jun 2018 06:53:52 -0700 (PDT) X-Google-Smtp-Source: ADUXVKL+/sK+xWgNIFOn1yHepSc+AEwmXCZaIHUlqX68qHGVMNXYlcm9efTSCqK7pQNEb7MY6dmz X-Received: by 2002:a17:902:b949:: with SMTP id h9-v6mr5628324pls.321.1529762032177; Sat, 23 Jun 2018 06:53:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529762032; cv=none; d=google.com; s=arc-20160816; b=xdJbJWeG2CZWOSAb9wlXTAnm/wnSNY30g0FGIuFKzxo7KQx+mfXuCqq+nQxlTqf47G A9EXKI5DxE1/7/O9A15U74fdrejQyqZ8wqB5++vAed3ElK0+0akzLhtefxklPNoyRF6X sZUo1XLJZtGR2CnrHEsqaMwX9ZonlzgTs7AiX2hb8EDJzp6R8T8KM4LQtBQkGir4mVPa /k9fBsvbBIaAcE/t34HoE6AgK0+dsEIXw1jFpipBMvBQhsediLs0cAiEzUZfbEvQhOlK MJSlTH1L8A7qCFh/TT60pWq1NK5EJGZINFkGZLLRbeRMLGiK9o7LYBi5fLxO364i0z8L Wd6Q== 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=DWL5rHoYYn5XVXquDBLeNkJ+vWh6bAmNE++tYs/TTT8=; b=Czv0WOWPGHP+dM5MZBlKMNoAxsU6Cex8408ozMpeLCrWvM5H65uPsTxgzdZCKtskGC NgBnN4FpXWXTd04TGEvS7DRsS16bJ3gyBG9WosOMt4IA8VIsUYyTAUXznE7tlptwNVFz 5Ly/yWdUy9zhIHMQuoVPe4oY8XwCrGG4h7YqmPchqzH9YZa0CGU3ZcT44TL+C+z3gJMK npkSflNKrJzoUzuahBOPSNCpGxoV/IUzvdXz6H+nOE9v1iP8xlmINizBsNHkedtW4PpY E/T/P299y0QBlRp3mf/ELqOTNQS2zPLyAGUMp5JJRZut3khchOCdhIIlrtjKUFT8ZSEl BX1w== 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 q23-v6si6348118pll.42.2018.06.23.06.52.59; Sat, 23 Jun 2018 06:53:52 -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 S1751661AbeFWNvH (ORCPT + 99 others); Sat, 23 Jun 2018 09:51:07 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:43370 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751326AbeFWNvF (ORCPT ); Sat, 23 Jun 2018 09:51:05 -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 1fWieb-0005xq-9i; Sat, 23 Jun 2018 15:32:37 +0200 Date: Sat, 23 Jun 2018 15:32:36 +0200 (CEST) From: Thomas Gleixner To: Pavel Tatashin cc: 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, peterz@infradead.org, prarit@redhat.com, feng.tang@intel.com, pmladek@suse.com, gnomes@lxorguk.ukuu.org.uk, linux-s390@vger.kernel.org Subject: Re: [PATCH v12 03/11] x86/tsc: redefine notsc to behave as tsc=unstable In-Reply-To: <20180621212518.19914-4-pasha.tatashin@oracle.com> Message-ID: References: <20180621212518.19914-1-pasha.tatashin@oracle.com> <20180621212518.19914-4-pasha.tatashin@oracle.com> 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 Thu, 21 Jun 2018, Pavel Tatashin wrote: > Currently, notsc kernel parameter disables the use of tsc register by > sched_clock(). However, this parameter does not prevent linux from > accessing tsc in other places in kernel. > > The only rational to boot with notsc is to avoid timing discrepancies on > multi-socket systems where different tsc frequencies may present, and thus > fallback to jiffies for clock source. > > However, there is another method to solve the above problem, it is to boot > with tsc=unstable parameter. This parameter allows sched_clock() to use tsc > but in case tsc is outside of expected interval it is corrected back to a > sane value. > > This is why there is no reason to keep notsc, and it can be removed. But, > for compatibility reasons we will keep this parameter but change its > definition to be the same as tsc=unstable. > > Signed-off-by: Pavel Tatashin > Reviewed-by: Dou Liyang Reviewed-by: Thomas Gleixner