From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752468AbdGDH10 (ORCPT ); Tue, 4 Jul 2017 03:27:26 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:46332 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752440AbdGDH1Z (ORCPT ); Tue, 4 Jul 2017 03:27:25 -0400 Date: Tue, 4 Jul 2017 09:27:12 +0200 (CEST) From: Thomas Gleixner To: Linus Torvalds cc: LKML , Andrew Morton , Ingo Molnar , "H. Peter Anvin" Subject: Re: [GIT pull] x86/timers updates for 4.13 In-Reply-To: Message-ID: References: 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: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 3 Jul 2017, Linus Torvalds wrote: > On Mon, Jul 3, 2017 at 1:20 AM, Thomas Gleixner wrote: > > > > This update contains: > > > > - The final solution for the TSC deadline timer borkage, which is caused > > by a hardware problem in the TSC_ADJUST/TSC_DEADLINE_TIMER logic. > > > > The problem is documented now fixed with a microcode update, so we can > > remove the workaround and check for the microcode version. If the > > microcode is not up to date, then the TSC deadline timer is > > enabled. If the borkage is fixed by the proper micro code version, > > then the deadline timer can be used. In both cases the restrictions to > > the range of the TSC_ADJUST value, which were added as workarounds, > > are removed. > > > > - A few simple fixes and updates to the timer related x86 code. > > That deadline timer explanation made no sense. Indeed. Sorry. > I edited it to what I think you wanted to say in the commit message. Yes. Thank you for fixing it up! tglx