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  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, 28 Jul 2014 08:52:55 +0200
From:	Peter Zijlstra <>
To:	"Yan, Zheng" <>
Subject: Re: [PATCH v3 6/9] perf, x86: handle multiple records in PEBS buffer

On Mon, Jul 28, 2014 at 10:24:30AM +0800, Yan, Zheng wrote:

> I don't think this method works for interrupt threshold > 1 case. When collision
> happens, the hardware only create one PEBS record. The status in next record has
> nothing to do with the collision record.

Andi previously stated that the hardware will always generate a record
for each event:

Please lock yourselves in room and do not come out until you can give a
straight and coherent answer.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists