summaryrefslogtreecommitdiffstats
path: root/Documentation/admin-guide/hw-vuln/cross-thread-rsb.rst
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-02-18 19:10:49 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2023-02-18 19:10:49 +0100
commit0c2822b116e300ca6e3b7f98623deb760a93a1d2 (patch)
treeaa767bb4071c6d59c1b53912ee06a2fd2250f560 /Documentation/admin-guide/hw-vuln/cross-thread-rsb.rst
parentMerge tag 'block-6.2-2023-02-17' of git://git.kernel.dk/linux (diff)
parentarm64: perf: reject CHAIN events at creation time (diff)
downloadlinux-0c2822b116e300ca6e3b7f98623deb760a93a1d2.tar.xz
linux-0c2822b116e300ca6e3b7f98623deb760a93a1d2.zip
Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Pull arm64 regression fix from Will Deacon: "Apologies for the _extremely_ late pull request here, but we had a 'perf' (i.e. CPU PMU) regression on the Apple M1 reported on Wednesday [1] which was introduced by bd2756811766 ("perf: Rewrite core context handling") during the merge window. Mark and I looked into this and noticed an additional problem caused by the same patch, where the 'CHAIN' event (used to combine two adjacent 32-bit counters into a single 64-bit counter) was not being filtered correctly. Mark posted a series on Thursday [2] which addresses both of these regressions and I queued it the same day. The changes are small, self-contained and have been confirmed to fix the original regression. Summary: - Fix 'perf' regression for non-standard CPU PMU hardware (i.e. Apple M1)" * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux: arm64: perf: reject CHAIN events at creation time arm_pmu: fix event CPU filtering
Diffstat (limited to 'Documentation/admin-guide/hw-vuln/cross-thread-rsb.rst')
0 files changed, 0 insertions, 0 deletions