Modify the SW tail logic in OA
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | drm/xe/xe_oa: Clear status only if relevant bits are setdrivers/ | +5 | 0 replies | |
| 2/3 | drm/xe/xe_oa: Avoid checking and setting fields in the OA reportdrivers/ | +2 | 0 replies | |
| 3/3 | drm/xe/xe_oa: Add a lag to the reports that is exported to userdrivers/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Modify the SW tail logic in OA
OA unit updates the HW TAIL register to indicate that a new report is available, although it does not guarantee that the report is visible in memory. Also the currently running workload contributes to some latency in seeing this report in memory. In the past we would set some fields in the OA report and check if the fields are populated to non-zero values by the HW, but this is no longer sufficient since some parts of the report may land out of order under heavy workloads. Drop this WA and add a new logic that just waits for a fixed number of HW TAIL report increments before returning data to the user. User will always see the reports lagging by this fixed number, however we do not have realtime use cases for OAG since OAG reports are mainly post processed.
v2: Rebase
Umesh Nerlige Ramappa (3):
drm/xe/xe_oa: Clear status only if relevant bits are set drm/xe/xe_oa: Avoid checking and setting fields in the OA report drm/xe/xe_oa: Add a lag to the reports that is exported to user
drivers/gpu/drm/xe/xe_oa.c | 94 +++++--------------------------------- 1 file changed, 12 insertions(+), 82 deletions(-)
Signature · 1 line
2.51.0