linux-kernel - Re: [PATCH 1/2] x86, perf: Remove warning for zero PEBS status

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: <20151203212833.GA17308@twins.programming.kicks-ass.net>
Date:	Thu, 3 Dec 2015 22:28:33 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, mingo@...nel.org,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 1/2] x86, perf: Remove warning for zero PEBS status

On Thu, Dec 03, 2015 at 01:22:19PM -0800, Andi Kleen wrote:
> From: Andi Kleen <ak@...ux.intel.com>
> 
> The recent change 75f80859b1 (... Robustify PEBS buffer drain)
> causes lots of warnings on different CPUs before Skylake
> when running PEBS intensive workloads.
> 
> They can have a zero status field in the PEBS record when
> PEBS is racing with clearing of GLOBAl_STATUS.

Ah, so _that_ is the explanation! Please put that in a comment near that
code. This has long puzzled me.

Thanks for digging into that.
--
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/