Prev: [PATCH] staging: clean up code a bit, use kernel native methods
Next: perf: export tracepoint events via sysfs: iwlwifi and iwlwifi_io
From: Steven Rostedt on 22 Jul 2010 09:30
On Thu, 2010-07-22 at 19:12 +0800, Lin Ming wrote:
> Below tracepoint events are exported under /sys/kernel/events/.
> sched, raw_syscalls, irq, timer, signal, workqueue, lock and bkl
>

>
> +/*
> + * tracepoint events: sched, raw_syscalls, irq, timer, signal,
> + * workqueue, lock and bkl are exported to
> + * /sys/kernel/events/
> + */
> +static void perf_sys_add_kernel_events(void)
> +{
> + if (!sys_kernel_events_kobj)
> + return;
> +
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "raw_syscalls");
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "sched");
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "irq");
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "timer");
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "signal");
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "workqueue");
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "lock");
> + perf_sys_add_tp_events(sys_kernel_events_kobj, "bkl");

Why are these hard-coded and not create by the event system types?

-- Steve

> +}
> +


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] staging: clean up code a bit, use kernel native methods
Next: perf: export tracepoint events via sysfs: iwlwifi and iwlwifi_io