From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: kan.liang@linux.intel.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] perf/x86/intel/uncore: Fix the scale of IIO free running counters on SNR
Date: Sat, 26 Apr 2025 09:23:35 -0400 [thread overview]
Message-ID: <20250426042117-2492bd6ce9e8ab32@stable.kernel.org> (raw)
In-Reply-To: <20250424233501.676485-1-kan.liang@linux.intel.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 96a720db59ab330c8562b2437153faa45dac705f
WARNING: Author mismatch between patch and upstream commit:
Backport author: kan.liang@linux.intel.com
Commit author: Kan Liang<kan.liang@linux.intel.com>
Status in newer kernel trees:
6.14.y | Present (different SHA1: 389ee3afddf6)
6.12.y | Present (different SHA1: 8d19c4a3b811)
6.6.y | Present (different SHA1: aea923afeae4)
6.1.y | Present (different SHA1: 8a809a8bcb89)
5.15.y | Present (different SHA1: 95ee595e4dfd)
Note: The patch differs from the upstream commit:
---
1: 96a720db59ab3 ! 1: 0a7c40d042397 perf/x86/intel/uncore: Fix the scale of IIO free running counters on SNR
@@ Metadata
## Commit message ##
perf/x86/intel/uncore: Fix the scale of IIO free running counters on SNR
+ [ Upstream commit 96a720db59ab330c8562b2437153faa45dac705f ]
+
+ (The existing patch in queue-5.10 was wrong.
+ queue-5.10/perf-x86-intel-uncore-fix-the-scale-of-iio-free-running-counters-on-snr.patch
+ It's supposed to change the array snr_uncore_iio_freerunning_events[]
+ rather than icx_uncore_iio_freerunning_events[]. Send the patch to
+ replace the wrong one.
+ With this fix the https://lore.kernel.org/stable/2025042139-protector-rickety-a72d@gregkh/
+ can be applied then.)
+
There was a mistake in the SNR uncore spec. The counter increments for
every 32 bytes of data sent from the IO agent to the SOC, not 4 bytes
which was documented in the spec.
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2025-04-26 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 23:35 [PATCH 5.10.y] perf/x86/intel/uncore: Fix the scale of IIO free running counters on SNR kan.liang
2025-04-26 13:23 ` Sasha Levin [this message]
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=20250426042117-2492bd6ce9e8ab32@stable.kernel.org \
--to=sashal@kernel.org \
--cc=kan.liang@linux.intel.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