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:	Tue, 8 Oct 2013 21:24:48 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Cc:	David Ahern <dsahern@...il.com>,
	Namhyung Kim <namhyung@...nel.org>,
	linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung.kim@....com>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 2/3] perf stat: Don't require a workload when using
 system wide or CPU options


* Arnaldo Carvalho de Melo <acme@...stprotocols.net> wrote:

> Em Tue, Oct 08, 2013 at 02:51:13PM +0200, Ingo Molnar escreveu:
> > Btw., would anyone be interested in adding CPU and node binding options to 
> > perf stat?
> > 
> > There's code to do something like that in tools/perf/bench/numa.c:
> > 
> >         /* Special option string parsing callbacks: */
> >         OPT_CALLBACK('C', "cpus", NULL, "cpu[,cpu2,...cpuN]",
> >                         "bind the first N tasks to these specific cpus (the rest is unbound)",
> >                         parse_cpus_opt),
> >         OPT_CALLBACK('M', "memnodes", NULL, "node[,node2,...nodeN]",
> >                         "bind the first N tasks to these specific memory nodes (the rest is unbound)",
> >                         parse_nodes_opt),
> 
> As a convenience to using:
> 
> 	taskset -c cpu-list perf stat -C cpu-list workload
> 
> ?

Yeah, something like that would be handy I think.

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ