linux-kernel - Re: [PATCH v1 4/5] perf: Introduce address range filtering

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, 25 Apr 2016 15:19:59 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc:	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	vince@...ter.net, eranian@...gle.com,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Mathieu Poirier <mathieu.poirier@...aro.org>
Subject: Re: [PATCH v1 4/5] perf: Introduce address range filtering

On Fri, Apr 22, 2016 at 07:19:11PM +0300, Alexander Shishkin wrote:
> @@ -393,12 +405,64 @@ struct pmu {
>  	void (*free_aux)		(void *aux); /* optional */
>  
>  	/*
> +	 * Validate address range filters: make sure hw supports the
> +	 * requested configuration and number of filters; return 0 if the
> +	 * supplied filters are valid, -errno otherwise.
> +	 */
> +	int (*addr_filters_validate)	(struct list_head *filters);
> +					/* optional */
> +
> +	/*
> +	 * Synchronize address range filter configuration:
> +	 * translate hw-agnostic filter into hardware configuration in
> +	 * event::hw::addr_filters.
> +	 */
> +	void (*addr_filters_sync)	(struct perf_event *event);
> +					/* optional */

So these two are not serialized the 'normal' way right? Does that want
more comment?