diff options
| author | Michal Wajdeczko <michal.wajdeczko@intel.com> | 2025-05-28 11:00:21 +0200 |
|---|---|---|
| committer | Michal Wajdeczko <michal.wajdeczko@intel.com> | 2025-06-02 19:22:03 +0200 |
| commit | d65650a9d153c91f0cde0f5026268812e0b697f3 (patch) | |
| tree | c405c963b65707c14b564260654cc0a04f858914 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | eae784475896cbd3faa2063cb2bed6cd8e085abf (diff) | |
drm/xe/guc: Resend potentially lost H2G MMIO request
There could be a scenario where the VF driver is resuming faster
than the driver PF is able to complete the VF FLR sequence which
includes reset of the VF scratch registers. This may result in
deletion of the ongoing HXG message (it could be either a host
request or a GuC response).
When we detect that HXG message was likey lost (scratch register
with HXG header was zeroed) try to send this request once more
before giving up.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Reviewed-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Link: https://lore.kernel.org/r/20250528090021.329-1-michal.wajdeczko@intel.com
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions