linux-kernel - RE: [PATCH V7 6/8] perf,tools: Dump per-sample freq/CPU%/CORE

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, 31 Aug 2015 19:10:44 +0000
From:	"Liang, Kan" <kan.liang@...el.com>
To:	Jiri Olsa <jolsa@...hat.com>
CC:	"acme@...nel.org" <acme@...nel.org>,
	"jolsa@...nel.org" <jolsa@...nel.org>,
	"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
	"luto@...nel.org" <luto@...nel.org>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"eranian@...gle.com" <eranian@...gle.com>,
	"ak@...ux.intel.com" <ak@...ux.intel.com>,
	"mark.rutland@....com" <mark.rutland@....com>,
	"Hunter, Adrian" <adrian.hunter@...el.com>,
	"namhyung@...nel.org" <namhyung@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V7 6/8] perf,tools: Dump per-sample freq/CPU%/CORE_BUSY%
 in report -D



> On Fri, Aug 28, 2015 at 05:48:07AM -0400, Kan Liang wrote:
> > From: Kan Liang <kan.liang@...el.com>
> >
> > The group read results from cycles/ref-cycles/TSC/ASTATE/MSTATE
> event
> > can be used to calculate the frequency, CPU Utilization and percent
> > performance during each sampling period.
> > This patch shows them in report -D.
> >
> > Here is an example:
> >
> > $ perf record -e
> > '{cycles,ref-cycles,msr/tsc/,msr/mperf/,msr/aperf/}:S' ~/tchain_edit
> 
> so this perf cord set of events is set when you want to get the freq
> data/ratios.. I think we should not force user to specify this on command
> line and provide short option for that like
> 
>   $ perf record --freq ~/tchain_edit
> 
> we already do this in perf stat for transactions.. you can also check the
> existence of particular events and warn user appropriatelly if any is missing
> 
Yes, we can do that, but should be in separate patch.

Thanks,
Kan
--
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/