linux-kernel - Re: [PATCH V4 5/8] perf/x86/intel/uncore: add infrastructure for free running counter

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: <alpine.DEB.2.20.1801142151440.2371@nanos>
Date:   Sun, 14 Jan 2018 21:52:20 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Kan Liang <kan.liang@...el.com>
cc:     peterz@...radead.org, mingo@...hat.com,
        linux-kernel@...r.kernel.org, acme@...nel.org, eranian@...gle.com,
        ak@...ux.intel.com
Subject: Re: [PATCH V4 5/8] perf/x86/intel/uncore: add infrastructure for
 free running counter

On Thu, 2 Nov 2017, kan.liang@...el.com wrote:

> From: Kan Liang <Kan.liang@...el.com>
> 
> The free running counter is read-only and always active. Current generic
> uncore code does not support this kind of counters.
> 
> The free running counter is read-only. It cannot be enable/disable in
> event_start/stop.
> The free running counter event and free running counter are 1:1 mapped.
> It doesn't need to be assigned nor tracked by event_list.
> The free running counters are always active. It doesn't need to check
> the free running counters' availability.
> 
> Use inline helpers to check fixed counter index and free running counter
> index.
>

That changelog is horrible to read. Other than that:

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>