[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1295630906.12215.4244.camel@gandalf.stny.rr.com>
Date: Fri, 21 Jan 2011 12:28:26 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Vincent Guittot <vincent.guittot@...aro.org>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
linux-kernel@...r.kernel.org, linux-hotplug@...r.kernel.org,
amit.kucheria@...aro.org
Subject: Re: [PATCH V2] tracing, perf : add cpu hotplug trace events
On Fri, 2011-01-21 at 09:43 +0100, Vincent Guittot wrote:
> On 20 January 2011 17:11, Frederic Weisbecker <fweisbec@...il.com> wrote:
> >
> >> +DEFINE_EVENT(cpu_hotplug, cpu_hotplug_arch_wait_die_start,
> >> +
> >> + TP_PROTO(unsigned int cpuid),
> >> +
> >> + TP_ARGS(cpuid)
> >> +);
> >> +
> >> +DEFINE_EVENT(cpu_hotplug, cpu_hotplug_arch_wait_die_end,
> >> +
> >> + TP_PROTO(unsigned int cpuid),
> >> +
> >> + TP_ARGS(cpuid)
> >> +);
> >
> > What is wait die, compared to die for example?
> >
>
> The arch_wait_die is used to trace the process which waits for the cpu
> to die (__cpu_die) and the arch_die is used to trace when the cpu dies
> (cpu_die)
Shouldn't that be "cpu_hotplug_arch_task_wait_die" then? If it is a task
that is waiting?
-- Steve
>
> > We need those tracepoints to be applied to get that reviewable in practice.
> >
>
> Ok, I'm going to send a proposal
>
> > Thanks.
> >
--
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