diff options
| author | John Harrison <John.C.Harrison@Intel.com> | 2023-09-21 11:20:33 -0700 |
|---|---|---|
| committer | John Harrison <John.C.Harrison@Intel.com> | 2023-10-03 18:48:07 -0700 |
| commit | 6a3ecfd4a04d800e291e1652ce1f22eff613e8ec (patch) | |
| tree | 1b8763fe4b9077fe618d7d3bf7e6fb2e7a7afd6d /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 6b8ace7a14e7926b7b914ccd96a8ac657c0d518c (diff) | |
drm/i915/guc: Suppress 'ignoring reset notification' message
If an active context has been banned (e.g. Ctrl+C killed) then it is
likely to be reset as part of evicting it from the hardware. That
results in a 'ignoring context reset notification: banned = 1'
message at info level. This confuses/concerns people and makes them
think something has gone wrong when it hasn't.
There is already a debug level message with essentially the same
information. So drop the 'ignore' info level one and just add the
'ignore' flag to the debug level one instead (which will therefore not
appear by default but will still show up in CI runs).
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230921182033.135448-1-John.C.Harrison@Intel.com
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions