diff options
| author |   Ville Syrjälä <ville.syrjala@linux.intel.com> | 2020-10-07 15:03:27 +0300 |
|---|---|---|
| committer | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2020-10-16 19:44:45 +0300 |
| commit | 2c1e63bab43081f462fa2ea2f9a5eed232876c1e (patch) | |
| tree | 22799ee6917de8358fbfb6669c6bb2bac7daf8e5 /drivers/gpu/drm/i915/display/intel_dp_mst.c | |
| parent | drm/i915: Apply WAC6entrylatency to kbl/cfl (diff) | |
| download | wireguard-linux-2c1e63bab43081f462fa2ea2f9a5eed232876c1e.tar.xz wireguard-linux-2c1e63bab43081f462fa2ea2f9a5eed232876c1e.zip | |
drm/i915: Mark initial fb obj as WT on eLLC machines to avoid rcu lockup during fbdev init
Currently we leave the cache_level of the initial fb obj
set to NONE. This means on eLLC machines the first pin_to_display()
will try to switch it to WT which requires a vma unbind+bind.
If that happens during the fbdev initialization rcu does not
seem operational which causes the unbind to get stuck. To
most appearances this looks like a dead machine on boot.
Avoid the unbind by already marking the object cache_level
as WT when creating it. We still do an excplicit ggtt pin
which will rewrite the PTEs anyway, so they will match whatever
cache level we set.
Cc: <stable@vger.kernel.org> # v5.7+
Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2381
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20201007120329.17076-1-ville.syrjala@linux.intel.com
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'drivers/gpu/drm/i915/display/intel_dp_mst.c')
0 files changed, 0 insertions, 0 deletions