All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Wayne Boyer <wayne.boyer@intel.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, "Goel,
	Akash" <akash.goel@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Pin the ifbdev for the info->system_base GGTT mmapping
Date: Fri, 09 Oct 2015 15:00:02 +0300	[thread overview]
Message-ID: <874mi06ym5.fsf@intel.com> (raw)
In-Reply-To: <20151009091109.GJ27939@nuc-i3427.alporthouse.com>

On Fri, 09 Oct 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Thu, Oct 08, 2015 at 01:50:21PM -0700, Wayne Boyer wrote:
>> From: Chris Wilson <chris@chris-wilson.co.uk>
>> 
>> 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: rebased on latest nightly (Wayne)
>> v3: changed i915_gem_object_ggtt_pin() to i915_gem_obj_ggtt_pin() based
>> on Chris' review. (Wayne)
>
> Note that this patch also depends on the
>
> 	drm/i915: Set the map-and-fenceable flag for preallocated objects
>
> fix as well
> http://patchwork.freedesktop.org/patch/58026/

Jesse, please provide your Tested-by on that plus this patch, since you
reported the breakage [1] that got the two patches reverted in the first
place.

Thanks,
Jani.


[1] http://mid.gmane.org/55DF3886.1060001@virtuousgeek.org

> -Chris
>
> -- 
> Chris Wilson, Intel Open Source Technology Centre
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Wayne Boyer <wayne.boyer@intel.com>,
	"Jesse Barnes" <jbarnes@virtuousgeek.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, stable@vger.kernel.org, "Goel\,
	Akash" <akash.goel@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Pin the ifbdev for the info->system_base GGTT mmapping
Date: Fri, 09 Oct 2015 15:00:02 +0300	[thread overview]
Message-ID: <874mi06ym5.fsf@intel.com> (raw)
In-Reply-To: <20151009091109.GJ27939@nuc-i3427.alporthouse.com>

On Fri, 09 Oct 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Thu, Oct 08, 2015 at 01:50:21PM -0700, Wayne Boyer wrote:
>> From: Chris Wilson <chris@chris-wilson.co.uk>
>> 
>> 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: rebased on latest nightly (Wayne)
>> v3: changed i915_gem_object_ggtt_pin() to i915_gem_obj_ggtt_pin() based
>> on Chris' review. (Wayne)
>
> Note that this patch also depends on the
>
> 	drm/i915: Set the map-and-fenceable flag for preallocated objects
>
> fix as well
> http://patchwork.freedesktop.org/patch/58026/

Jesse, please provide your Tested-by on that plus this patch, since you
reported the breakage [1] that got the two patches reverted in the first
place.

Thanks,
Jani.


[1] http://mid.gmane.org/55DF3886.1060001@virtuousgeek.org

> -Chris
>
> -- 
> Chris Wilson, Intel Open Source Technology Centre
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2015-10-09 11:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 16:48 [PATCH] drm/i915: Pin the ifbdev for the info->system_base GGTT mmapping Chris Wilson
2015-08-26  8:23 ` Deepak
2015-10-02 22:16   ` Boyer, Wayne
2015-10-06  8:25     ` Daniel Vetter
2015-10-07 18:34       ` Wayne Boyer
2015-10-07 18:34         ` Wayne Boyer
2015-10-08  9:07         ` Chris Wilson
2015-10-08 14:45           ` Jesse Barnes
2015-10-08 14:45             ` Jesse Barnes
2015-10-08 20:50           ` Wayne Boyer
2015-10-09  9:11             ` Chris Wilson
2015-10-09 12:00               ` Jani Nikula [this message]
2015-10-09 12:00                 ` [Intel-gfx] " Jani Nikula
2015-10-23 21:17             ` Dave Gordon
2015-10-30 16:18               ` Daniel Vetter
2015-10-30 17:17                 ` Chris Wilson
2015-10-25 14:34             ` Lukas Wunner
2015-10-25 14:34               ` [Intel-gfx] " Lukas Wunner
2015-10-25 14:53             ` Lukas Wunner
2015-10-25 14:53               ` [Intel-gfx] " Lukas Wunner
2015-08-26 11:55 ` [PATCH] drm/i915: Set the map-and-fenceable flag for preallocated objects Chris Wilson
2015-08-26 13:06   ` Daniel Vetter
2015-08-26 13:08     ` Daniel Vetter
2015-08-26 13:08       ` Daniel Vetter
2015-08-26 13:51     ` Chris Wilson
2015-08-27  8:36     ` Jani Nikula
2015-08-27  8:36       ` [Intel-gfx] " Jani Nikula
2015-08-27 16:19       ` Jesse Barnes
2015-08-27 16:19         ` [Intel-gfx] " Jesse Barnes
2015-08-27 16:36         ` Chris Wilson
2015-08-28  7:00           ` Jani Nikula
2015-08-28  7:00             ` [Intel-gfx] " Jani Nikula
2015-08-30 18:28   ` shuang.he

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874mi06ym5.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=akash.goel@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=stable@vger.kernel.org \
    --cc=wayne.boyer@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.