linux-kernel - Re: [PATCH v3 00/10] Add support for parameterized events from sysfs

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]

Date:	Mon, 22 Sep 2014 16:43:19 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>, ak@...ux.intel.com,
	peterz@...radead.org, eranian@...gle.com,
	Paul Mackerras <paulus@...ba.org>, dev@...yps.com,
	Michael Ellerman <michaele@....ibm.com>,
	Anshuman Khandual <khandual@...ux.vnet.ibm.com>,
	hbabu@...ibm.com, linux-kernel@...r.kernel.org,
	linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH v3 00/10] Add support for parameterized events from sysfs

On Wed, Sep 17, 2014 at 11:51:53AM -0700, Sukadev Bhattiprolu wrote:

SNIP

> 
> 	This means that when provided as an event, a value for
> 	phys_processor_idx must also be supplied. For example:
> 
> 	  perf stat -e 'hv_gpci/dtbp_ptitc,phys_processor_idx=0x2/' ...
> 
> Changelog[v3]
> 	- [Jiri Olsa] Changed the event parameters are specified. If
> 	  event file specifes 'param=val' make the usage 'param=123'
> 	  rather than 'val=123'. (patch 1,2/10)
> 	- Shortened event names using "PHYS" and "VCPU" (patch 4/10)
> 	- Print help message if invalid parameter is specified or required
> 	  parameter is missing.
> 	- Moved 3 patches that are unrelated to parametrized events into
> 	  a separate patchset.
> 	- Reordered patches so code changes come first.

hi,
Could you please rebase to latest acme/perf/core?
There were some changes in util/pmu.c conflicting with yours..

thanks,
jirka
--
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/