linux-kernel - Re: [RFC/PATCH] perf sched: Implement 'perf sched runtime' command

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 24 Aug 2015 23:19:44 -0700
From:	David Ahern <dsahern@...il.com>
To:	Namhyung Kim <namhyung@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...nel.org>
CC:	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jiri Olsa <jolsa@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC/PATCH] perf sched: Implement 'perf sched runtime' command

On 8/24/15 11:11 PM, Namhyung Kim wrote:
>
> +static int perf_sched__read_runtime_events(struct perf_sched *sched)
> +{
> +	const struct perf_evsel_str_handler handlers[] = {
> +		{ "sched:sched_switch",	      process_sched_switch_event, },
> +		{ "sched:sched_stat_runtime", process_sched_runtime_event, },
> +		{ "sched:sched_stat_sleep",   process_sched_sleep_event, },
> +		{ "sched:sched_stat_wait",    process_sched_wait_event, },
> +		{ "sched:sched_stat_iowait",  process_sched_iowait_event, },
> +		{ "sched:sched_migrate_task", process_sched_migrate_task_event, },
> +	};

I like the concept (obviously since I have invested so much time in 
other solutions). But... you cannot rely on the sched_stat tracepoints 
being enabled. I believe it is a performance hit to have 
CONFIG_SCHEDSTATS enabled and distributions (e.g., Fedora) do not have 
it enabled.
--
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/