Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752162AbbFCAV6 (ORCPT ); Tue, 2 Jun 2015 20:21:58 -0400 Received: from mail-lb0-f182.google.com ([209.85.217.182]:33928 "EHLO mail-lb0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750836AbbFCAVt (ORCPT ); Tue, 2 Jun 2015 20:21:49 -0400 MIME-Version: 1.0 In-Reply-To: <20150602233820.GP1187@tassilo.jf.intel.com> References: <1432194944-29087-1-git-send-email-adrian.hunter@intel.com> <20150602194350.GN1187@tassilo.jf.intel.com> <20150602202037.GO1187@tassilo.jf.intel.com> <20150602233820.GP1187@tassilo.jf.intel.com> From: Andy Lutomirski Date: Tue, 2 Jun 2015 17:21:27 -0700 Message-ID: Subject: Re: [PATCH RFC] x86, tsc: Allow for high latency in quick_pit_calibrate() To: Andi Kleen Cc: Thomas Gleixner , Adrian Hunter , LKML , Linus Torvalds , X86 ML , "H. Peter Anvin" , Len Brown Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 28 On Tue, Jun 2, 2015 at 4:38 PM, Andi Kleen wrote: > On Tue, Jun 02, 2015 at 11:03:26PM +0200, Thomas Gleixner wrote: >> >> >> On Tue, 2 Jun 2015, Andi Kleen wrote: >> >> > > There's the code in tsc_msr.c. It should be relatively >> > > straightforward to extend it to cover everything that intel_pstate >> > > supports. >> > >> > That's a good idea, but we still need an always working fallback when the >> > model number is not available. So Adrian's patch is needed in any >> > case. >> >> Nonsense. The slow calibration is already a working fallback. > > Please read Adrian's description again. It's not working when the PIT read is > too slow. That is when the new algorithm is needed. > tglx's suggestion was to use slow calibration as a fallback. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/