From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753486AbdA3NG3 (ORCPT <rfc822;w@1wt.eu>);
        Mon, 30 Jan 2017 08:06:29 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:58839 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752951AbdA3NEu (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 30 Jan 2017 08:04:50 -0500
Date: Mon, 30 Jan 2017 14:04:46 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: Henning Schild <henning.schild@siemens.com>
cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Borislav Petkov <bp@alien8.de>, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [3/8] x86/tsc: Store and check TSC ADJUST MSR
In-Reply-To: <20170130131301.7ddae08d@md1em3qc>
Message-ID: <alpine.DEB.2.20.1701301404160.3606@nanos>
References: <20161119134017.655323776@linutronix.de> <20170127143632.4f56d927@md1em3qc> <alpine.DEB.2.20.1701301113120.3606@nanos> <20170130131301.7ddae08d@md1em3qc>
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: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 30 Jan 2017, Henning Schild wrote:
> On Mon, 30 Jan 2017 11:20:25 +0100
> Thomas Gleixner <tglx@linutronix.de> wrote:
> > There is nothing you can ever be sure about, but I doubt that the
> > ADJUST MSR is going to vanish.
> 
> That sounds very much like i expected. But assuming the MSR has come to
> stay, the problem should be solved for recent kernels and Intel-CPUs.
> 
> The AMD-Manual from 12/16 does not mention that MSR. I do not have
> access to an AMD machine. But i can only assume that bigger machines
> also suffer from async TSCs and basically all fall back to HPET.

Borislav?