From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [1/8] drm/i915: Hack and slash, throttle execbuffer hogs (rev2)
Date: Thu, 07 Feb 2019 08:08:06 -0000 [thread overview]
Message-ID: <20190207080806.31507.27114@emeril.freedesktop.org> (raw)
In-Reply-To: <20190207071829.5574-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/8] drm/i915: Hack and slash, throttle execbuffer hogs (rev2)
URL : https://patchwork.freedesktop.org/series/56328/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Hack and slash, throttle execbuffer hogs
Okay!
Commit: drm/i915: Defer removing fence register tracking to rpm wakeup
Okay!
Commit: drm/i915: Revoke mmaps and prevent access to fence registers across reset
-drivers/gpu/drm/i915/i915_gem.c:986:39: warning: expression using sizeof(void)
-drivers/gpu/drm/i915/i915_gem.c:986:39: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/i915_gem.c:986:39: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/i915_gem.c:986:39: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/i915_reset.c:1303:5: warning: context imbalance in 'i915_reset_trylock' - different lock contexts for basic block
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3565:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3559:16: warning: expression using sizeof(void)
Commit: drm/i915: Force the GPU reset upon wedging
Okay!
Commit: drm/i915: Uninterruptibly drain the timelines on unwedging
Okay!
Commit: drm/i915: Wait for old resets before applying debugfs/i915_wedged
Okay!
Commit: drm/i915: Serialise resets with wedging
Okay!
Commit: drm/i915: Don't claim an unstarted request was guilty
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-07 8:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 7:18 [PATCH 1/8] drm/i915: Hack and slash, throttle execbuffer hogs Chris Wilson
2019-02-07 7:18 ` [PATCH 2/8] drm/i915: Defer removing fence register tracking to rpm wakeup Chris Wilson
2019-02-07 13:22 ` Mika Kuoppala
2019-02-07 13:38 ` Chris Wilson
2019-02-07 14:09 ` Mika Kuoppala
2019-02-07 14:13 ` Chris Wilson
2019-02-07 7:18 ` [PATCH 3/8] drm/i915: Revoke mmaps and prevent access to fence registers across reset Chris Wilson
2019-02-07 15:05 ` Mika Kuoppala
2019-02-07 7:18 ` [PATCH 4/8] drm/i915: Force the GPU reset upon wedging Chris Wilson
2019-02-08 9:31 ` Mika Kuoppala
2019-02-08 9:47 ` Chris Wilson
2019-02-07 7:18 ` [PATCH 5/8] drm/i915: Uninterruptibly drain the timelines on unwedging Chris Wilson
2019-02-08 9:46 ` Mika Kuoppala
2019-02-08 10:00 ` Chris Wilson
2019-02-08 15:07 ` Mika Kuoppala
2019-02-08 15:13 ` Chris Wilson
2019-02-07 7:18 ` [PATCH 6/8] drm/i915: Wait for old resets before applying debugfs/i915_wedged Chris Wilson
2019-02-08 9:56 ` Mika Kuoppala
2019-02-08 10:01 ` Chris Wilson
2019-02-07 7:18 ` [PATCH 7/8] drm/i915: Serialise resets with wedging Chris Wilson
2019-02-08 14:30 ` Mika Kuoppala
2019-02-07 7:18 ` [PATCH 8/8] drm/i915: Don't claim an unstarted request was guilty Chris Wilson
2019-02-07 7:41 ` [PATCH] " Chris Wilson
2019-02-08 14:47 ` Mika Kuoppala
2019-02-08 14:58 ` Chris Wilson
2019-02-08 15:31 ` Mika Kuoppala
2019-02-07 8:08 ` Patchwork [this message]
2019-02-07 8:25 ` ✓ Fi.CI.BAT: success for series starting with [1/8] drm/i915: Hack and slash, throttle execbuffer hogs (rev2) Patchwork
2019-02-07 9:53 ` ✓ Fi.CI.IGT: " Patchwork
2019-02-07 16:01 ` [PATCH 1/8] drm/i915: Hack and slash, throttle execbuffer hogs Joonas Lahtinen
2019-02-07 16:05 ` Chris Wilson
2019-02-07 16:21 ` 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=20190207080806.31507.27114@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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