[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151202124531.GC9928@worktop.ger.corp.intel.com>
Date: Wed, 2 Dec 2015 13:45:31 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Chris Metcalf <cmetcalf@...hip.com>,
Thomas Gleixner <tglx@...utronix.de>,
Luiz Capitulino <lcapitulino@...hat.com>,
Christoph Lameter <cl@...ux.com>,
Ingo Molnar <mingo@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Rik van Riel <riel@...hat.com>
Subject: Re: [PATCH 2/7] nohz: New tick dependency mask
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists