linux-kernel - Re: [RFC][PATCH v1 04/15] perf: export tracepoint events via sysfs: sched, raw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1279805273.3319.0.camel@gandalf.stny.rr.com>
Date:	Thu, 22 Jul 2010 09:27:53 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Robert Richter <robert.richter@....com>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Johannes Berg <johannes@...solutions.net>,
	Peter Zijlstra <peterz@...radead.org>,
	Greg KH <greg@...ah.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Paul Mundt <lethal@...ux-sh.org>,
	"eranian@...il.com" <eranian@...il.com>,
	"Gary.Mohr@...l.com" <Gary.Mohr@...l.com>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Paul Mackerras <paulus@...ba.org>,
	"David S. Miller" <davem@...emloft.net>,
	Russell King <rmk+kernel@....linux.org.uk>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Will Deacon <will.deacon@....com>,
	Maynard Johnson <mpjohn@...ibm.com>,
	Carl Love <carll@...ibm.com>,
	Kay Sievers <kay.sievers@...y.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC][PATCH v1 04/15] perf: export tracepoint events via
 sysfs: sched, raw_syscalls etc.

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/