From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1032818AbdDTOlz (ORCPT ); Thu, 20 Apr 2017 10:41:55 -0400 Received: from merlin.infradead.org ([205.233.59.134]:53364 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967046AbdDTOlx (ORCPT ); Thu, 20 Apr 2017 10:41:53 -0400 Date: Thu, 20 Apr 2017 16:41:46 +0200 From: Peter Zijlstra To: Daniel Lezcano Cc: ville.syrjala@linux.intel.com, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, "Rafael J . Wysocki" Subject: Re: [PATCH] Revert "cpuidle: Replace ktime_get() with local_clock()" Message-ID: <20170420144146.fuoqagm6xxrpxfoo@hirez.programming.kicks-ass.net> References: <20170420124447.13716-1-ville.syrjala@linux.intel.com> <20170420130813.h7dycr5cptbrvdkz@hirez.programming.kicks-ass.net> <20170420143751.GE2523@mai> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170420143751.GE2523@mai> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 20, 2017 at 04:37:51PM +0200, Daniel Lezcano wrote: > > > > + sched_clock_idle_wakeup_event(0); > > + > > Is it planned to skip this if the tsc is reliable? Yes. Current code doesn't quite do that, but if you follow that link I send earlier, I'm about to fix that (again). Now, if only this Core2 piece of crap would actually boot a recent kernel, I could go figure out wth is wrong.. :/