On Fri, 2011-01-21 at 09:43 +0100, Vincent Guittot wrote: > On 20 January 2011 17:11, Frederic Weisbecker <fweisbec@xxxxxxxxx> 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-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
