From: Greg KH <gregkh@linuxfoundation.org>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: stable@vger.kernel.org, Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH] KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
Date: Thu, 12 Dec 2024 08:57:58 +0100 [thread overview]
Message-ID: <2024121244-mannish-hermit-526d@gregkh> (raw)
In-Reply-To: <20241203190236.2711302-1-rananta@google.com>
On Tue, Dec 03, 2024 at 07:02:36PM +0000, Raghavendra Rao Ananta wrote:
> commit 54bbee190d42166209185d89070c58a343bf514b upstream.
>
> DDI0487K.a D13.3.1 describes the PMU overflow condition, which evaluates
> to true if any counter's global enable (PMCR_EL0.E), overflow flag
> (PMOVSSET_EL0[n]), and interrupt enable (PMINTENSET_EL1[n]) are all 1.
> Of note, this does not require a counter to be enabled
> (i.e. PMCNTENSET_EL0[n] = 1) to generate an overflow.
>
> Align kvm_pmu_overflow_status() with the reality of the architecture
> and stop using PMCNTENSET_EL0 as part of the overflow condition. The
> bug was discovered while running an SBSA PMU test [*], which only sets
> PMCR.E, PMOVSSET<0>, PMINTENSET<0>, and expects an overflow interrupt.
>
> Cc: stable@vger.kernel.org
> Fixes: 76d883c4e640 ("arm64: KVM: Add access handler for PMOVSSET and PMOVSCLR register")
> Link: https://github.com/ARM-software/sbsa-acs/blob/master/test_pool/pmu/operating_system/test_pmu001.c
> Signed-off-by: Raghavendra Rao Ananta <rananta@google.com>
> [ oliver: massaged changelog ]
> Reviewed-by: Marc Zyngier <maz@kernel.org>
> Link: https://lore.kernel.org/r/20241120005230.2335682-2-oliver.upton@linux.dev
> Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
> ---
> virt/kvm/arm/pmu.c | 1 -
> 1 file changed, 1 deletion(-)
What branch is this patch for?
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-12 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 15:05 FAILED: patch "[PATCH] KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow" failed to apply to 4.19-stable tree gregkh
2024-12-03 19:02 ` [PATCH] KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status Raghavendra Rao Ananta
2024-12-03 23:34 ` Sasha Levin
2024-12-12 7:57 ` Greg KH [this message]
2024-12-12 8:27 ` Greg KH
2024-12-12 17:41 ` Raghavendra Rao Ananta
2024-12-12 18:07 ` Greg KH
2024-12-12 18:52 ` Raghavendra Rao Ananta
2024-12-13 7:22 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-12-16 17:54 Raghavendra Rao Ananta
2024-12-17 0:42 ` Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024121244-mannish-hermit-526d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=rananta@google.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox