hwlat-detector: Have it actually find hardware latency
Status from this message: Applied, thanks.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | hwlat-detector: Update hwlat_detector to add outer loop detectiondrivers/ | +26 | 0 replies | |
| 2/3 | hwlat-detector: Use trace_clock_local if availabledrivers/ | +25 | 0 replies | |
| 3/3 | hwlat-detector: Use thread instead of stop machinedrivers/ | +25 | 0 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Steven Rostedt |
|---|---|
| Series | A-b |
| 1/3 | |
| 2/3 | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH RT 0/3] hwlat-detector: Have it actually find hardware latency
Thi patch series fixes up hwlat-detector to check the entire path of time for a latency being hit, instead of the quick check between two time stamps.
It also uses the trace_local_clock() if available, which is much lighter weight than ktime_get() which might produce false positives. As the trace clock is used to detect irq latencies, it's suitable for hardware latency.
Finally, stop machine is removed and the test is run by a single thread.