@@ -196,6 +196,7 @@ static int intelfb_create(struct drm_fb_helper *helper,
struct drm_i915_gem_object *obj;
int size, ret;
bool prealloc = false;
+ bool fb_pinned = false;
if (intel_fb &&
(sizes->fb_width > intel_fb->base.width ||
@@ -213,6 +214,7 @@ static int intelfb_create(struct drm_fb_helper *helper,
if (ret)
return ret;
intel_fb = ifbdev->fb;
+ fb_pinned = true;
} else {
DRM_DEBUG_KMS("re-using BIOS fb\n");
prealloc = true;
@@ -225,6 +227,16 @@ static int intelfb_create(struct drm_fb_helper *helper,
mutex_lock(&dev->struct_mutex);
+ /* The fb constructor will have already pinned us (or inherited a
+ * GGTT region from the BIOS) suitable for a scanout, so
+ * this should just be a no-op and increment the pin count for the
+ * fbdev mmapping. It does have a useful side-effect of validating
+ * the pin for fbdev's use via a GGTT mmapping.
+ */
+ ret = i915_gem_obj_ggtt_pin(obj, 0, PIN_MAPPABLE);
+ if (ret)
+ goto out_unlock;
+
info = drm_fb_helper_alloc_fbi(helper);
if (IS_ERR(info)) {
DRM_ERROR("Failed to allocate fb_info\n");
@@ -286,7 +298,12 @@ static int intelfb_create(struct drm_fb_helper *helper,
out_destroy_fbi:
drm_fb_helper_release_fbi(helper);
out_unpin:
+ /* Once for info->screen_base mmaping... */
i915_gem_object_ggtt_unpin(obj);
+out_unlock:
+ if (fb_pinned)
+ /* ...and once for the intel_fb */
+ i915_gem_object_ggtt_unpin(obj);
mutex_unlock(&dev->struct_mutex);
return ret;
}
@@ -524,6 +541,8 @@ static const struct drm_fb_helper_funcs intel_fb_helper_funcs = {
static void intel_fbdev_destroy(struct drm_device *dev,
struct intel_fbdev *ifbdev)
{
+ /* Release the pinning for the info->screen_base mmaping. */
+ i915_gem_object_ggtt_unpin(ifbdev->fb->obj);
drm_fb_helper_unregister_fbi(&ifbdev->helper);
drm_fb_helper_release_fbi(&ifbdev->helper);
A long time ago (before 3.14) we relied on a permanent pinning of the ifbdev to lock the fb in place inside the GGTT. However, the introduction of stealing the BIOS framebuffer and reusing its address in the GGTT for the fbdev has muddied waters and we use an inherited fb. However, the inherited fb is only pinned whilst it is active and we no longer have an explicit pin for the info->system_base mmapping used by the fbdev. The result is that after some aperture pressure the fbdev may be evicted, but we continue to write the fbcon into the same GGTT address - overwriting anything else that may be put into that offset. The effect is most pronounced across suspend/resume as intel_fbdev_set_suspend() does a full clear over the whole scanout. v2: Only unpin the intel_fb is we allocate it. If we inherit the fb from the BIOS, we do not own the pinned vma (except for the reference we add in this patch for our access via info->screen_base). Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: "Goel, Akash" <akash.goel@intel.com> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Jesse Barnes <jbarnes@virtuousgeek.org> Cc: stable@vger.kernel.org --- drivers/gpu/drm/i915/intel_fbdev.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)