public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset
Date: Thu, 31 Jan 2019 12:17:38 -0000	[thread overview]
Message-ID: <20190131121738.16740.97943@emeril.freedesktop.org> (raw)
In-Reply-To: <20190131120105.23144-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset
URL   : https://patchwork.freedesktop.org/series/56042/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Sparse version: v0.5.2
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:1304:5: warning: context imbalance in 'i915_reset_lock' - different lock contexts for basic block
+drivers/gpu/drm/i915/i915_reset.c:1325:6: warning: context imbalance in 'i915_reset_unlock' - unexpected unlock
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3549:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3543: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!

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-01-31 12:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 12:01 [PATCH 1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset Chris Wilson
2019-01-31 12:01 ` [PATCH 2/5] drm/i915: Force the GPU reset upon wedging Chris Wilson
2019-01-31 12:01 ` [PATCH 3/5] drm/i915: Uninterruptibly drain the timelines on unwedging Chris Wilson
2019-01-31 12:01 ` [PATCH 4/5] drm/i915: Wait for old resets before applying debugfs/i915_wedged Chris Wilson
2019-01-31 12:01 ` [PATCH 5/5] drm/i915: Serialise resets with wedging Chris Wilson
2019-01-31 12:13   ` [PATCH] " Chris Wilson
2019-01-31 12:14   ` Chris Wilson
2019-01-31 12:17 ` Patchwork [this message]
2019-01-31 12:39 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset Patchwork
2019-01-31 12:40 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset (rev3) Patchwork
2019-01-31 12:59 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-01-31 13:12 ` [PATCH] drm/i915: Revoke mmaps and prevent access to fence registers across reset Chris Wilson
2019-01-31 13:23 ` ✗ Fi.CI.SPARSE: warning for series starting with drm/i915: Revoke mmaps and prevent access to fence registers across reset (rev4) Patchwork
2019-01-31 13:45 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-31 22:33 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-01-31 22:37   ` Chris Wilson
2019-02-01 21:25 ` [PATCH 1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset kbuild test robot

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=20190131121738.16740.97943@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