From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754438AbcHSOJr (ORCPT ); Fri, 19 Aug 2016 10:09:47 -0400 Received: from merlin.infradead.org ([205.233.59.134]:36258 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752435AbcHSOJq (ORCPT ); Fri, 19 Aug 2016 10:09:46 -0400 Date: Fri, 19 Aug 2016 16:09:28 +0200 From: Peter Zijlstra To: Steven Rostedt Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Andrew Morton , Clark Williams , Thomas Gleixner , Jon Masters , Daniel Wagner , Carsten Emde , Sebastian Andrzej Siewior Subject: Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Message-ID: <20160819140928.GK10121@twins.programming.kicks-ass.net> References: <20160810135356.265780824@goodmis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160810135356.265780824@goodmis.org> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 10, 2016 at 09:53:56AM -0400, Steven Rostedt wrote: > Changes since v1: > > . Added checks for CONFIG_GENERIC_SCHED_CLOCK, and if that is set, > only nmi_counts will be recorded when an NMI is triggered, but not > the time in NMI, because the generic sched_clock is not NMI safe. > (suggested by Sebastian Andrzej Siewior) So any of the platforms using GENERIC_SCHED_CLOCK _have_ NMIs ? In any case, for those you could probably use ktime_get_mono_fast_ns().