summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorTales A. Mendonça <talesam@gmail.com>2026-09-22 11:46:33 -0300
committerMatthew Brost <matthew.brost@intel.com>2026-09-24 14:20:15 -0700
commitfc668a6e9c5f2d9800947bdd3d027f000030bcbc (patch)
tree0de39c7407e22de119951b61d9f3dce65a4aa493 /tools/perf/scripts/python/bin
parent63360b328b1ffdcd561911c25c5e25f74ce97afe (diff)
downloadlinux-fc668a6e9c5f2d9800947bdd3d027f000030bcbc.tar.gz
linux-fc668a6e9c5f2d9800947bdd3d027f000030bcbc.zip
drm/xe: Log when a timed out TLB invalidation ack finally arrives
When a TLB invalidation fence times out we log the timeout, but if the ack for that seqno later shows up there is no record of it, making it impossible to tell from logs whether the ack was lost forever or merely (very) late. Track the most recent timed out seqno and log how late its ack arrives, relative to both the original request and the moment the fence was signaled with -ETIME. On ARL with GuC 70.53.0 this shows the acks are never lost: they consistently arrive ~2.3s after the request, tens of milliseconds after the TDR has already signaled the fence: TLB invalidation fence timeout, seqno=10992 recv=10991 TLB invalidation late ack: seqno=10992 recv=10992, request-to-ack=2314ms, timeout-to-ack=45ms Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/8678 Signed-off-by: Tales A. Mendonça <talesam@gmail.com> Reviewed-by: Matthew Brost <matthew.brost@intel.com> Signed-off-by: Matthew Brost <matthew.brost@intel.com> Link: https://patch.msgid.link/20260922144634.55130-3-talesam@gmail.com
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions