linux-kernel - Re: [PATCH V3 2/6] perf: Passing struct perf_event to function setup

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, 08 Aug 2016 13:49:40 +0300
From:	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:	Peter Zijlstra <peterz@...radead.org>,
	Mathieu Poirier <mathieu.poirier@...aro.org>
Cc:	acme@...nel.org, jolsa@...nel.org, mingo@...hat.com,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH V3 2/6] perf: Passing struct perf_event to function setup_aux()

Peter Zijlstra <peterz@...radead.org> writes:

> On Thu, Jul 28, 2016 at 03:42:19PM -0600, Mathieu Poirier wrote:
>> Some information, like driver specific configuration, is found
>> in the hw_perf_event  structure.  As such pass a 'struct perf_event'
>> to function setup_aux() rather than just the CPU number so that
>> individual drivers can make the right configuration when setting
>> up a session.
>> 
>> Signed-off-by: Mathieu Poirier <mathieu.poirier@...aro.org>
>> Cc: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
>
> Yeah, no objection to this.

Sure, but I'd like a commit message that actually describes *what*
information and *why*.

Regards,
--
Alex