linux-kernel - Re: [PATCH v4 0/9] perf, x86: large PEBS interrupt threshold

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]

Message-ID: <20140731071625.GA4209@gmail.com>
Date:	Thu, 31 Jul 2014 09:16:25 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	"Yan, Zheng" <zheng.z.yan@...el.com>
Cc:	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	acme@...radead.org, eranian@...gle.com, andi@...stfloor.org,
	Jiri Olsa <jolsa@...hat.com>
Subject: Re: [PATCH v4 0/9] perf, x86: large PEBS interrupt threshold


* Yan, Zheng <zheng.z.yan@...el.com> wrote:

> This patch series implements large PEBS interrupt threshold. For some
> limited cases, it can significantly reduce the sample overhead. Please
> read patch 6's commit message for more information.
> 
> changes since v1:
>   - drop patch 'perf, core: Add all PMUs to pmu_idr'
>   - add comments for case that multiple counters overflow simultaneously
> changes since v2:
>   - rename perf_sched_cb_{enable,disable} to perf_sched_cb_user_{inc,dec} 
>   - use flag to indicate auto reload mechanism
>   - move codes that setup PEBS sample data to separate function
>   - output the PEBS records in batch 
>   - enable this for All (PEBS capable) hardware 
>   - more description for the multiplex
> changes since v3:
>   - ignore conflicting PEBS record

Please include performance measurements, 'significantly reduces sample 
overhead' is a totally inadequate description to judge this patch set.

Please also include total diffstat in the 0/N mail.

Thanks,

	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/