[igt-dev] [PATCH i-g-t 3/3] runner: Read all kernel logs when there are logs

Chris Wilson chris at chris-wilson.co.uk
Thu Mar 12 10:09:49 UTC 2020


Quoting Petri Latvala (2020-03-12 09:59:44)
> Instead of reading one record at a time between select() calls and
> tainted-checks etc, use the same at-the-end dmesg dumper whenever
> there's activity in /dev/kmsg. It's possible that the occasional chunk
> of missing dmesg we're sometimes hitting is due to reading too slowly,
> especially if there's a huge gem traceback.
> 
> Also print a clear message if we hit a log buffer underrun so we know
> it.
> 
> Reference: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/79
> Signed-off-by: Petri Latvala <petri.latvala at intel.com>

Looks reasonable, the proof is in the pudding.
Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>
for the series.
-Chris


More information about the igt-dev mailing list