linux-kernel - Re: [PATCH v3 6/6] KVM: x86/vPMU: Add lazy mechanism to release perf

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: <d3434a16-07ed-7070-f316-9a2fa072ace0@redhat.com>
Date:   Tue, 22 Oct 2019 16:09:02 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Like Xu <like.xu@...ux.intel.com>, kvm@...r.kernel.org
Cc:     peterz@...radead.org, like.xu@...el.com,
        linux-kernel@...r.kernel.org, jmattson@...gle.com,
        sean.j.christopherson@...el.com, wei.w.wang@...el.com,
        kan.liang@...el.com
Subject: Re: [PATCH v3 6/6] KVM: x86/vPMU: Add lazy mechanism to release
 perf_event per vPMC

On 22/10/19 14:00, Like Xu wrote:
> 
> Second, the structure of pmu->pmc_in_use is in the following format:
> 
>   Intel: [0 .. INTEL_PMC_MAX_GENERIC-1] <=> gp counters
>             [INTEL_PMC_IDX_FIXED .. INTEL_PMC_IDX_FIXED + 2] <=> fixed
>   AMD:   [0 .. AMD64_NUM_COUNTERS-1] <=> gp counters

Sorry---I confused INTEL_PMC_MAX_FIXED and INTEL_PMC_IDX_FIXED.

The patches look good, I'll give them another look since I obviously
wasn't very much awake when reviewing them.

Paolo