mlxbf-pmc: Fix crspace event offsets
Bug #2043005 reported by
Shravan Kumar Ramani
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-bluefield (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
SRU Justification:
[Impact]
Currently, the offsets calculated for programming crspace type events on BlueField-3 are incorrect and this leads to a mismatch of counter numbers between the driver and actual HW where, for example, event2 in the driver is actually event4 in HW.
[Fix]
Fix the offset calculation for programming crspace events.
[Test Case]
On a BlueField-3 platform, program any valid event number to the event sysfs and check that the corresponding counter value increments.
[Regression Potential]
This is a bug fix and the regression potential can be considered minimal.
Changed in linux-bluefield (Ubuntu): | |
status: | New → Invalid |
Changed in linux-bluefield (Ubuntu Jammy): | |
status: | New → Fix Committed |
tags: |
added: verification-done-jammy-linux-bluefield removed: verification-needed-jammy-linux-bluefield |
To post a comment you must log in.
This bug is awaiting verification that the linux-bluefield /5.15.0- 1032.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy-linux- bluefield' to 'verification- done-jammy- linux-bluefield '. If the problem still exists, change the tag 'verification- needed- jammy-linux- bluefield' to 'verification- failed- jammy-linux- bluefield' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!