New PMU fixes for marked events.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Joseph Salisbury | ||
Zesty |
Fix Released
|
Medium
|
Joseph Salisbury |
Bug Description
== SRU Justification ==
The current Zesty kernel does not enable marked events on Power9. The
following fixes are required:
101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")
09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
Commit 101dd590a7fa was added to mainline in v4.13-rc3 and commit 09539f9b1236
was added in v4.13-rc4.
== Fixes ==
commit 101dd590a7fa379
Author: Nicholas Piggin <email address hidden>
Date: Mon Jul 10 16:19:38 2017 +1000
powerpc/perf: Avoid spurious PMU interrupts after idle
commit 09539f9b123652e
Author: Nicholas Piggin <email address hidden>
Date: Thu Jul 20 11:53:22 2017 +1000
powerpc/perf: POWER9 PMU stops after idle workaround
== Regression Potential ==
Low, since these commits are specific to powerpc.
Dear Canonical,
Please include the following fixes into Ubuntu Zesty (4.10) kernel. The current kernel does not enable marked events on Power9. And the following fixes are required:
09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")
CVE References
tags: | added: architecture-ppc64le bugnameltc-158551 severity-medium targetmilestone-inin16043 |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → linux (Ubuntu) |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
Changed in linux (Ubuntu Zesty): | |
status: | New → Triaged |
description: | updated |
Changed in linux (Ubuntu): | |
assignee: | Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Zesty): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
status: | Triaged → In Progress |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
Changed in ubuntu-power-systems: | |
status: | New → Triaged |
Changed in ubuntu-power-systems: | |
status: | Triaged → In Progress |
tags: | added: triage-g |
description: | updated |
Changed in linux (Ubuntu Zesty): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
status: | Fix Committed → In Progress |
tags: |
added: verification-done-zesty removed: verification-needed-zesty |
Changed in ubuntu-power-systems: | |
status: | In Progress → Fix Released |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
I built a Zesty test kernel with a pick of commits 101dd590a7fa( 4.13-rc3) and 09539f9(4.13-rc4). The test kernel can be downloaded from:
http:// kernel. ubuntu. com/~jsalisbury /lp1716491/
Can you test this kernel and see if it resolves this bug?
Thanks in advance!