linux-kernel - Re: [PATCH] perf, x86: Allow setting period 1

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]

Message-ID: <20130415112655.GA26300@gmail.com>
Date:	Mon, 15 Apr 2013 13:26:55 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Andi Kleen <andi@...stfloor.org>, a.p.zijlstra@...llo.nl,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf, x86: Allow setting period 1


* Andi Kleen <ak@...ux.intel.com> wrote:

> On Wed, Apr 10, 2013 at 02:58:08PM +0200, Ingo Molnar wrote:
> > 
> > * Andi Kleen <andi@...stfloor.org> wrote:
> > 
> > > From: Andi Kleen <ak@...ux.intel.com>
> > > 
> > > I had some requests for setting period 1, so that every event of something
> > > is caught.  To my knowledge there is no limit to 1 on Intel hardware.
> > > Just remove the check for minimum 2
> > > 
> > > If specific CPUs have problems we can black list them.
> > 
> > How have you tested this? The commit that added this quirk mentions very high perf 
> > load triggering badness unless this quirk is added.
> 
> Profiling a couple of simple loads on Westmere and IvyBridge: mostly AIM7 and 
> kernel builds. You can get throttling of course, but no excessive load.
> 
> The original quirk was done long ago before the modern event throttling 
> infrastructure may have been completely in place, right?

The failure IIRC wasn't about throttling or not, it was about extreme profiling 
(lots of copies of perf record, perf top, perf stat running in parallel, mixed -a 
and workload-local options), eventually resulting in a messed up PMU.

So before we can remove that a similar test should be repeated and made sure that 
no badness happens, on a wide enough range of systems.

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/