From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Unpin framebuffers when crtc is deconfigured.
Date: Wed, 18 Nov 2015 09:52:32 +0100 [thread overview]
Message-ID: <564C3C50.4040007@linux.intel.com> (raw)
In-Reply-To: <20151117185407.GW16848@phenom.ffwll.local>
Op 17-11-15 om 19:54 schreef Daniel Vetter:
> On Wed, Nov 04, 2015 at 02:43:31PM +0100, Maarten Lankhorst wrote:
>> When setcrtc is called and steals the last connector away from a crtc
>> it's turned off because it can't stay configured without connectors.
>>
>> The framebuffer is still preserved however, and that causes troubles
>> in the IGT stress test kms_flip.flips-vs-fences which tries to use
>> as many pins as possible and hangs on the third crtc because of
>> framebuffer pins on the first 2 crtc's.
>>
>> Cc: stable@vger.kernel.org #v4.3
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> drm_atomic_helper_set_config clears the fb for the primary plane if we
> clear the mode. Where is the leak?
Steal the last connector from another crtc. The crtc is deconfigured because it has no connectors any more, its the planes are left untouched.
> Also where exactly does it hang - we should have plenty of fences left for
> 3x2 pinned framebuffers. If you allow more than 2 pinned fb per plane then
> that's a bug somewhere with pageflips getting ahead of the unpin worker.
> -Daniel
>
Just try that stress test, it submits max_fences-a few so you will get -ENOSPC because it ran out out of fences. :)
~Maarten
prev parent reply other threads:[~2015-11-18 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1446644611-26532-1-git-send-email-maarten.lankhorst@linux.intel.com>
2015-11-17 18:54 ` [Intel-gfx] [PATCH] drm/i915: Unpin framebuffers when crtc is deconfigured Daniel Vetter
2015-11-18 8:52 ` Maarten Lankhorst [this message]
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=564C3C50.4040007@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).