diff options
| author | Alan Previn <alan.previn.teres.alexis@intel.com> | 2022-06-06 17:23:14 -0700 |
|---|---|---|
| committer | John Harrison <John.C.Harrison@Intel.com> | 2022-07-06 14:38:56 -0700 |
| commit | b94a1a207de5e06a55b5a8259073fd8d1637f093 (patch) | |
| tree | 52a2ff49b66a83ed8c427bb1d91b229b88d80843 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | 1926a6b75954fc1a8b44d10bd0c67db957b78cf7 (diff) | |
drm/i915/guc: Asynchronous flush of GuC log regions
Both error-capture and relay-logging mechanism use the GuC
log infrastructure. That means the KMD must send a log flush
complete notification back to GuC after reading the data out.
This call is currently being sent synchronously.
However, synchronous H2Gs cause problems when the system is
backed up. There is no need for this to be synchronous. The
KMD wasn't even looking at the return status from it. So make
it asynchronous and then there is no issue about time outs.
Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220607002314.1451656-2-alan.previn.teres.alexis@intel.com
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions