linux-kernel - Re: [patch] perf wrong enabled time after attach/enable/enable

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]

Date:   Fri, 4 Aug 2017 09:35:57 -0400 (EDT)
From:   Vince Weaver <vincent.weaver@...ne.edu>
To:     Peter Zijlstra <peterz@...radead.org>
cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Stephane Eranian <eranian@...il.com>
Subject: Re: [patch] perf wrong enabled time after attach/enable/enable

On Fri, 4 Aug 2017, Peter Zijlstra wrote:

>   Testing if userspace rdpmc reads are supported...          NEW BEHAVIOR
>   Testing if rdpmc fallback works on sw events...            PASSED
>   Testing if userspace rdpmc reads give expected results...  PASSED
> 
> is that 'NEW BEHAVIOR' thing something I should worry about?

no, sorry, I've been working on cleaning up the outputs of the tests to be 
less confusing.

NEW BEHAVIOR here means it has the "new" (since Linux 3.12) cap_usr_rdpmc 
bit layout.

Vince