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: <20140731072744.GN19379@twins.programming.kicks-ass.net>
Date:	Thu, 31 Jul 2014 09:27:44 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	"Yan, Zheng" <zheng.z.yan@...el.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...nel.org, acme@...radead.org,
	eranian@...gle.com, andi@...stfloor.org
Subject: Re: [PATCH v4 0/9] perf, x86: large PEBS interrupt threshold

OK, so no feedback on the 'pending' discussions we had wrt PEBS record
generation?

No feedback on the correctness aspects of the overflow crap?

Just a new series, which I then have to dig through to figure out wtf
changed?

A quick look at patch 6 reads like you still don't understand the issue
right. There are no 'collisions' as such in PEBS record generation, or
are there? See the earlier open discussion.

_WHY_ are you sending me new patches without sorting the open points
first?

Content of type "application/pgp-signature" skipped