From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752059AbdGDBGF (ORCPT ); Mon, 3 Jul 2017 21:06:05 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:36739 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750980AbdGDBGD (ORCPT ); Mon, 3 Jul 2017 21:06:03 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Mon, 3 Jul 2017 18:06:02 -0700 X-Google-Sender-Auth: P6e2Engq06oAykuhpmIx1YHRzcI Message-ID: Subject: Re: [GIT pull] x86/timers updates for 4.13 To: Thomas Gleixner Cc: LKML , Andrew Morton , Ingo Molnar , "H. Peter Anvin" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. I edited it to what I think you wanted to say in the commit message. Linus