From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752208AbbFDHRh (ORCPT ); Thu, 4 Jun 2015 03:17:37 -0400 Received: from terminus.zytor.com ([198.137.202.10]:43096 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751577AbbFDHR3 (ORCPT ); Thu, 4 Jun 2015 03:17:29 -0400 Message-ID: <556FFB81.8080507@zytor.com> Date: Thu, 04 Jun 2015 00:17:21 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Len Brown , Andy Lutomirski CC: X86 ML , Linux PM list , "linux-kernel@vger.kernel.org" , Len Brown Subject: Re: [PATCH 1/1] x86 TSC: set X86_FEATURE_TSC_RELIABLE, per CPUID References: <556CA704.1070000@kernel.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/01/2015 05:45 PM, Len Brown wrote: > > BTW, it also begs the question if Linux could actually *repair* the BIOS damage? > We may very well be able to by setting the TSC offset register to zero on all CPUs. -hpa