From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH 0/7] gpu reset and page_flip removal, take 2
Date: Thu, 20 Jul 2017 19:57:47 +0200 [thread overview]
Message-ID: <20170720175754.30751-1-daniel.vetter@ffwll.ch> (raw)
Hi all,
I landed the locking change, which fixes the gpu reset deadlocks at least for
anything modern (and non-igt). Would be great if we can get the first patch
landed fast, just to address the regression in CI and get rid of the dmesg-warn.
Currently we're blind to dmesg noise in a lot of gpu hang tests and that's not
all that good (the timeout based wedging has a DRM_ERROR, which I think is the
right thing for unexpected delays).
The remaining patches, especially patch 3, probably need a bunch more soaking
time. I think 4-7 are ready for merging, not much pointing in holding them up
due to lack of boosting in atomic.
As usual, review&testing very much welcome.
Thanks,
Daniel
Daniel Vetter (7):
drm/i915: Avoid the gpu reset vs. modeset deadlock
drm/i915: Push i915_sw_fence_wait into the nonblocking atomic commit
drm/i915: More surgically unbreak the modeset vs reset deadlock
drm/i915: Rip out legacy page_flip completion/irq handling
drm/i915: adjust has_pending_fb_unpin to atomic
drm/i915: Remove intel_flip_work infrastructure
drm/i915: Drop unpin stall in atomic_prepare_commit
drivers/gpu/drm/i915/i915_debugfs.c | 70 ------
drivers/gpu/drm/i915/i915_drv.c | 1 -
drivers/gpu/drm/i915/i915_drv.h | 7 +-
drivers/gpu/drm/i915/i915_gem.c | 2 -
drivers/gpu/drm/i915/i915_irq.c | 151 ++-----------
drivers/gpu/drm/i915/intel_display.c | 424 +++++------------------------------
drivers/gpu/drm/i915/intel_drv.h | 26 +--
drivers/gpu/drm/i915/intel_sprite.c | 8 +-
8 files changed, 88 insertions(+), 601 deletions(-)
--
2.13.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2017-07-20 17:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 17:57 Daniel Vetter [this message]
2017-07-20 17:57 ` [PATCH 1/7] drm/i915: Avoid the gpu reset vs. modeset deadlock Daniel Vetter
2017-07-20 19:47 ` Chris Wilson
2017-07-20 20:04 ` Daniel Vetter
2017-07-20 20:16 ` Chris Wilson
2017-07-20 20:18 ` Daniel Vetter
2017-07-20 17:57 ` [PATCH 2/7] drm/i915: Push i915_sw_fence_wait into the nonblocking atomic commit Daniel Vetter
2017-08-03 19:44 ` Michel Thierry
2017-08-07 15:33 ` Daniel Vetter
2017-08-07 17:06 ` Michel Thierry
2017-07-20 17:57 ` [PATCH 3/7] drm/i915: More surgically unbreak the modeset vs reset deadlock Daniel Vetter
2017-08-03 19:35 ` Michel Thierry
2017-08-07 15:39 ` Daniel Vetter
2017-07-20 17:57 ` [PATCH 4/7] drm/i915: Rip out legacy page_flip completion/irq handling Daniel Vetter
2017-07-20 17:57 ` [PATCH 5/7] drm/i915: adjust has_pending_fb_unpin to atomic Daniel Vetter
2017-07-20 17:57 ` [PATCH 6/7] drm/i915: Remove intel_flip_work infrastructure Daniel Vetter
2017-07-20 17:57 ` [PATCH 7/7] drm/i915: Drop unpin stall in atomic_prepare_commit Daniel Vetter
2017-07-20 20:47 ` Daniel Vetter
2017-07-20 18:14 ` ✓ Fi.CI.BAT: success for gpu reset and page_flip removal, take 2 Patchwork
2017-07-20 19:45 ` 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=20170720175754.30751-1-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--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