From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH v3]PM/Sleep: Timer quiesce in freeze state Date: Mon, 26 Jan 2015 15:50:21 +0100 Message-ID: <2076277.JWdUtd56Il@vostro.rjw.lan> References: <54866625.8010406@linux.intel.com> <2137807.aqSxQQCuJ3@vostro.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit Return-path: Received: from v094114.home.net.pl ([79.96.170.134]:55159 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755624AbbAZO1i (ORCPT ); Mon, 26 Jan 2015 09:27:38 -0500 In-Reply-To: Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: Thomas Gleixner Cc: "Li, Aubrey" , Peter Zijlstra , "Brown, Len" , "alan@linux.intel.com" , LKML , Linux PM list On Monday, January 26, 2015 03:24:27 PM Thomas Gleixner wrote: > On Mon, 26 Jan 2015, Rafael J. Wysocki wrote: > > On Monday, January 26, 2015 10:40:24 AM Thomas Gleixner wrote: > > > The only remaining issue might be a NMI calling into > > > ktime_get_mono_fast_ns() before timekeeping is resumed. Its probably a > > > non issue on x86/tsc, but it might be a problem on other platforms > > > which turn off devices, clocks, It's not rocket science to prevent > > > that. > > > > I don't see any users of ktime_get_mono_fast_ns() at all, unless some non-trivial > > macros are involved. At least grepping for it only returns the definition, > > declarations and the line in trace.c. > > You can trace in NMI and perf is going to use ktime_get_mono_fast_ns() > eventually as well. So I'm not sure how to intercept that to be honest. Any hints? Rafael