[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174958165124.102860.1466726781633621770.b4-ty@google.com>
Date: Tue, 10 Jun 2025 12:42:15 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>,
Dapeng Mi <dapeng1.mi@...ux.intel.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Jim Mattson <jmattson@...gle.com>, Mingwei Zhang <mizhang@...gle.com>,
Zide Chen <zide.chen@...el.com>, Das Sandipan <Sandipan.Das@....com>,
Shukla Manali <Manali.Shukla@....com>, Dapeng Mi <dapeng1.mi@...el.com>
Subject: Re: [PATCH] x86/pmu_pebs: Initalize and enable PMU interrupt (PMI_VECTOR)
On Thu, 24 Apr 2025 05:22:01 +0000, Dapeng Mi wrote:
> PMU interrupt is not correctly initialized and enabled in pmu_pebs test.
> It leads to the APIC_LVTPC mask bit is never cleared after first PMI and
> all subsequential PEBS PMIs are suppressed.
>
> Although it doesn't impact pmu_pebs test results since current pmu_pebs
> test checks PEBS records by polling instead of PMI driving, it's still an
> incorrect behavior and could cause some unexpected false positives.
>
> [...]
Applied to kvm-x86 next, thanks!
[1/1] x86/pmu_pebs: Initalize and enable PMU interrupt (PMI_VECTOR)
https://github.com/kvm-x86/kvm-unit-tests/commit/389dfda487f9
--
https://github.com/kvm-x86/kvm-unit-tests/tree/next
Powered by blists - more mailing lists