From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Date: Fri, 21 Jan 2011 17:28:26 +0000 Subject: Re: [PATCH V2] tracing, perf : add cpu hotplug trace events Message-Id: <1295630906.12215.4244.camel@gandalf.stny.rr.com> List-Id: References: <20110120161101.GA17218@nowhere> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Vincent Guittot Cc: Frederic Weisbecker , linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org, amit.kucheria@linaro.org On Fri, 2011-01-21 at 09:43 +0100, Vincent Guittot wrote: > On 20 January 2011 17:11, Frederic Weisbecker 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. > >