From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 5/5] drm/i915: Make wait_for_flips interruptible.
Date: Tue, 21 Jul 2015 15:59:25 +0200 [thread overview]
Message-ID: <55AE503D.9040607@linux.intel.com> (raw)
In-Reply-To: <20150721133117.GJ6166@nuc-i3427.alporthouse.com>
Op 21-07-15 om 15:31 schreef Chris Wilson:
> On Tue, Jul 21, 2015 at 02:33:33PM +0200, Maarten Lankhorst wrote:
>>>> + if (plane->type == DRM_PLANE_TYPE_PRIMARY && old_obj) {
>>> Would feel safer is we just asked if the CRTC had pending flips
>>> irrespective of old_obj. Do you plan on moving the pending flips from
>>> CRTC to plane? That would seem to be implied here.
>> This preserves old behavior since page flips can only happen on primary planes.
>> Do you want cursor updates to wait on pending primary flips?
> Cursor updates need to be serialized with primary updates, yes (or else
> there are some fun scenarios in which you can hang the display engine).
Ok but right now we don't sync this.. won't blocking on flips for moving the mouse in Xorg be bad for performance?
> What I was actually thinking was using plane->state for tracking the
> flips. Having just reread what I wrote that didn't come across. I would
> rather see fewer primary_plane special cases and more no-ops on
> secondary planes. I think you will end up using such infrastructure
> on the secondary planes eventually.
I think the current infrastructure will die eventually and perhaps be done asynchronously. I just don't know yet what will replace it.
>>>> + /* Big Hammer, we also need to ensure that any pending
>>>> + * MI_WAIT_FOR_EVENT inside a user batch buffer on the
>>>> + * current scanout is retired before unpinning the old
>>>> + * framebuffer. Note that we rely on userspace rendering
>>>> + * into the buffer attached to the pipe they are waiting
>>>> + * on. If not, userspace generates a GPU hang with IPEHR
>>>> + * point to the MI_WAIT_FOR_EVENT.
>>>> + *
>>>> + * This should only fail upon a hung GPU, in which case we
>>>> + * can safely continue.
>>>> + */
>>>> + if (!ret && plane->type == DRM_PLANE_TYPE_PRIMARY && old_obj)
>>>> + ret = i915_gem_object_wait_rendering(old_obj, true);
>>> Technically I can create a batch with a WAIT_ON_EVENT for a secondary
>>> plane as well. This path need only be done in a modeset, not for a
>>> simple plane flip. (But we actually need to serialise with rendering to
>>> old_obj before regarding the plane flip as complete.) Is there a
>>> plane-prepare-modeset hook?
>> The comment didn't explain that, is hiding this behind a needs_modeset(crtc_state) sufficient here?
> For the purpose of limiting the wait to when the pipe dimensions may
> change, yes.
Is that only needed during full modesets, or when changing PIPESRC too?
~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-21 13:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 12:57 [PATCH 0/5] drm/i915: Make waiting interruptible Maarten Lankhorst
2015-07-16 12:57 ` [PATCH 1/5] drm/i915: Handle return value in intel_pin_and_fence_fb_obj Maarten Lankhorst
2015-07-21 11:31 ` Chris Wilson
2015-07-21 14:09 ` [PATCH v1.1 1/5] drm/i915: Handle return value in intel_pin_and_fence_fb_obj, v2 Maarten Lankhorst
2015-07-24 13:26 ` Ander Conselvan De Oliveira
2015-07-24 14:02 ` Chris Wilson
2015-07-26 7:24 ` Maarten Lankhorst
2015-07-16 12:57 ` [PATCH 2/5] drm/atomic: Make prepare_fb/cleanup_fb only take state Maarten Lankhorst
2015-07-16 14:13 ` [PATCH v1.1 2/5] drm/atomic: Make prepare_fb/cleanup_fb only take state, v2 Maarten Lankhorst
2015-07-22 13:23 ` Rob Clark
2015-07-27 7:53 ` [Intel-gfx] " Daniel Vetter
2015-07-27 11:07 ` Maarten Lankhorst
2015-07-27 11:14 ` Daniel Vetter
2015-07-27 11:55 ` [Intel-gfx] " Maarten Lankhorst
2015-07-16 12:57 ` [PATCH 3/5] drm/i915: Make prepare_plane_fb fully interruptible Maarten Lankhorst
2015-07-16 12:57 ` [PATCH 4/5] drm/i915: Remove wait_for_pending_flips from disable_noatomic Maarten Lankhorst
2015-07-21 11:35 ` Chris Wilson
2015-07-21 12:38 ` Maarten Lankhorst
2015-07-21 12:40 ` Chris Wilson
2015-07-21 12:47 ` Maarten Lankhorst
2015-07-16 12:57 ` [PATCH 5/5] drm/i915: Make wait_for_flips interruptible Maarten Lankhorst
2015-07-20 14:52 ` Maarten Lankhorst
2015-07-21 6:51 ` Daniel Vetter
2015-07-21 8:02 ` Maarten Lankhorst
2015-07-21 11:26 ` Chris Wilson
2015-07-21 12:33 ` Maarten Lankhorst
2015-07-21 13:31 ` Chris Wilson
2015-07-21 13:59 ` Maarten Lankhorst [this message]
2015-07-21 14:39 ` Chris Wilson
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=55AE503D.9040607@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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