From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758457AbbLBOKJ (ORCPT ); Wed, 2 Dec 2015 09:10:09 -0500 Received: from mail-wm0-f54.google.com ([74.125.82.54]:36685 "EHLO mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755186AbbLBOKH (ORCPT ); Wed, 2 Dec 2015 09:10:07 -0500 Date: Wed, 2 Dec 2015 15:10:03 +0100 From: Frederic Weisbecker To: Peter Zijlstra Cc: LKML , Chris Metcalf , Thomas Gleixner , Luiz Capitulino , Christoph Lameter , Ingo Molnar , Viresh Kumar , Rik van Riel Subject: Re: [PATCH 2/7] nohz: New tick dependency mask Message-ID: <20151202141002.GC14766@lerouge> References: <1447424529-13671-1-git-send-email-fweisbec@gmail.com> <1447424529-13671-3-git-send-email-fweisbec@gmail.com> <20151201204109.GN17308@twins.programming.kicks-ass.net> <20151201222025.GA31973@lerouge> <20151202124531.GC9928@worktop.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151202124531.GC9928@worktop.ger.corp.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 02, 2015 at 01:45:31PM +0100, Peter Zijlstra wrote: > On Tue, Dec 01, 2015 at 11:20:28PM +0100, Frederic Weisbecker wrote: > > > > > +static void trace_tick_dependency(unsigned long dep) > > > > +{ > > > > + if (dep & TICK_POSIX_TIMER_MASK) { > > > > + trace_tick_stop(0, "posix timers running\n"); > > > > + return; > > > > + } > > > > + > > > > + if (dep & TICK_PERF_EVENTS_MASK) { > > > > + trace_tick_stop(0, "perf events running\n"); > > > > + return; > > > > + } > > > > + > > > > + if (dep & TICK_SCHED_MASK) { > > > > + trace_tick_stop(0, "more than 1 task in runqueue\n"); > > > > + return; > > > > + } > > > > + > > > > + if (dep & TICK_CLOCK_UNSTABLE_MASK) > > > > + trace_tick_stop(0, "unstable sched clock\n"); > > > > +} > > > > > > I would suggest ditching the strings and using the > > > > Using a code value instead? > > Duh, it seems I forgot to finish that sentence :/ > > I meant to say use the ftrace enum stuff. So yes, you encode a value and > the ftrace printing muck will generate a string if and when required. Right I first wanted to avoid that because it makes parsing more complicated for tools but probably it works fine now with libtraceevents.