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 [01/27] drm/i915: Flush context free work on cleanup
Date: Tue, 12 Nov 2019 10:23:25 -0000 [thread overview]
Message-ID: <157355420512.31295.11013729633903200475@emeril.freedesktop.org> (raw)
In-Reply-To: <20191112092854.869-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [01/27] drm/i915: Flush context free work on cleanup
URL : https://patchwork.freedesktop.org/series/69340/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/i915: Flush context free work on cleanup
Okay!
Commit: drm/i915/gt: Try an extra flush on the Haswell blitter
Okay!
Commit: drm/i915/gem: Silence sparse for RCU protection inside the constructor
Okay!
Commit: drm/i915/selftests: Mock the engine sorting for easy validation
Okay!
Commit: Revert "drm/i915: use a separate context for gpu relocs"
Okay!
Commit: drm/i915: Use a ctor for TYPESAFE_BY_RCU i915_request
Okay!
Commit: drm/i915: Drop GEM context as a direct link from i915_request
Okay!
Commit: drm/i915: Push the use-semaphore marker onto the intel_context
Okay!
Commit: drm/i915: Remove i915->kernel_context
Okay!
Commit: drm/i915: Move i915_gem_init_contexts() earlier
Okay!
Commit: drm/i915/uc: Use an internal buffer for firmware images
Okay!
Commit: drm/i915/gt: Pull GT initialisation under intel_gt_init()
Okay!
Commit: drm/i915/gt: Merge engine init/setup loops
Okay!
Commit: drm/i915/gt: Expose engine properties via sysfs
-
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:52:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:53:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:57:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:73:20: error: undefined identifier 'engine'
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:96:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
Commit: drm/i915/gt: Expose engine->mmio_base via sysfs
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:61:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:62:10: error: bad integer constant expression
-O:drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:52:10: error: bad integer constant expression
-O:drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:53:10: error: bad integer constant expression
Commit: drm/i915/gt: Expose timeslice duration to sysfs
Okay!
Commit: drm/i915/gt: Expose busywait duration to sysfs
+drivers/gpu/drm/i915/intel_wakeref.c:125:19: warning: context imbalance in 'wakeref_auto_timeout' - unexpected unlock
Commit: drm/i915/gt: Expose reset stop timeout via sysfs
Okay!
Commit: drm/i915/gt: Expose preempt reset timeout via sysfs
Okay!
Commit: drm/i915/gt: Expose heartbeat interval via sysfs
Okay!
Commit: drm/i915: Flush idle barriers when waiting
Okay!
Commit: drm/i915: Allow userspace to specify ringsize on construction
Okay!
Commit: drm/i915/gem: Honour O_NONBLOCK before throttling execbuf submissions
Okay!
Commit: drm/i915/gt: Set unused mocs entry to follow PTE on tgl as on all others
Okay!
Commit: drm/i915/gt: Tidy up debug-warns for the mocs control table
Okay!
Commit: drm/i915/gt: Refactor mocs loops into single control macro
Okay!
Commit: drm/i915/selftests: Add coverage of mocs registers
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [01/27] drm/i915: Flush context free work on cleanup
Date: Tue, 12 Nov 2019 10:23:25 -0000 [thread overview]
Message-ID: <157355420512.31295.11013729633903200475@emeril.freedesktop.org> (raw)
Message-ID: <20191112102325.d7RD35wuRMJBvg0Qml45ullOT0g2mzVec1cVD00M82o@z> (raw)
In-Reply-To: <20191112092854.869-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [01/27] drm/i915: Flush context free work on cleanup
URL : https://patchwork.freedesktop.org/series/69340/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/i915: Flush context free work on cleanup
Okay!
Commit: drm/i915/gt: Try an extra flush on the Haswell blitter
Okay!
Commit: drm/i915/gem: Silence sparse for RCU protection inside the constructor
Okay!
Commit: drm/i915/selftests: Mock the engine sorting for easy validation
Okay!
Commit: Revert "drm/i915: use a separate context for gpu relocs"
Okay!
Commit: drm/i915: Use a ctor for TYPESAFE_BY_RCU i915_request
Okay!
Commit: drm/i915: Drop GEM context as a direct link from i915_request
Okay!
Commit: drm/i915: Push the use-semaphore marker onto the intel_context
Okay!
Commit: drm/i915: Remove i915->kernel_context
Okay!
Commit: drm/i915: Move i915_gem_init_contexts() earlier
Okay!
Commit: drm/i915/uc: Use an internal buffer for firmware images
Okay!
Commit: drm/i915/gt: Pull GT initialisation under intel_gt_init()
Okay!
Commit: drm/i915/gt: Merge engine init/setup loops
Okay!
Commit: drm/i915/gt: Expose engine properties via sysfs
-
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:52:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:53:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:57:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:73:20: error: undefined identifier 'engine'
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:96:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
Commit: drm/i915/gt: Expose engine->mmio_base via sysfs
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:61:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:62:10: error: bad integer constant expression
-O:drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:52:10: error: bad integer constant expression
-O:drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:53:10: error: bad integer constant expression
Commit: drm/i915/gt: Expose timeslice duration to sysfs
Okay!
Commit: drm/i915/gt: Expose busywait duration to sysfs
+drivers/gpu/drm/i915/intel_wakeref.c:125:19: warning: context imbalance in 'wakeref_auto_timeout' - unexpected unlock
Commit: drm/i915/gt: Expose reset stop timeout via sysfs
Okay!
Commit: drm/i915/gt: Expose preempt reset timeout via sysfs
Okay!
Commit: drm/i915/gt: Expose heartbeat interval via sysfs
Okay!
Commit: drm/i915: Flush idle barriers when waiting
Okay!
Commit: drm/i915: Allow userspace to specify ringsize on construction
Okay!
Commit: drm/i915/gem: Honour O_NONBLOCK before throttling execbuf submissions
Okay!
Commit: drm/i915/gt: Set unused mocs entry to follow PTE on tgl as on all others
Okay!
Commit: drm/i915/gt: Tidy up debug-warns for the mocs control table
Okay!
Commit: drm/i915/gt: Refactor mocs loops into single control macro
Okay!
Commit: drm/i915/selftests: Add coverage of mocs registers
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-11-12 10:23 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 9:28 [PATCH 01/27] drm/i915: Flush context free work on cleanup Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 02/27] drm/i915/gt: Try an extra flush on the Haswell blitter Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 03/27] drm/i915/gem: Silence sparse for RCU protection inside the constructor Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 04/27] drm/i915/selftests: Mock the engine sorting for easy validation Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 05/27] Revert "drm/i915: use a separate context for gpu relocs" Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 06/27] drm/i915: Use a ctor for TYPESAFE_BY_RCU i915_request Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 07/27] drm/i915: Drop GEM context as a direct link from i915_request Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 08/27] drm/i915: Push the use-semaphore marker onto the intel_context Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 09/27] drm/i915: Remove i915->kernel_context Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 10/27] drm/i915: Move i915_gem_init_contexts() earlier Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 11/27] drm/i915/uc: Use an internal buffer for firmware images Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 12/27] drm/i915/gt: Pull GT initialisation under intel_gt_init() Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 13/27] drm/i915/gt: Merge engine init/setup loops Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 14/27] drm/i915/gt: Expose engine properties via sysfs Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 15/27] drm/i915/gt: Expose engine->mmio_base " Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-21 13:18 ` Lionel Landwerlin
2019-11-21 13:18 ` [Intel-gfx] " Lionel Landwerlin
2019-11-21 13:23 ` Chris Wilson
2019-11-21 13:23 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 16/27] drm/i915/gt: Expose timeslice duration to sysfs Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 17/27] drm/i915/gt: Expose busywait " Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 18/27] drm/i915/gt: Expose reset stop timeout via sysfs Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 19/27] drm/i915/gt: Expose preempt reset " Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 20/27] drm/i915/gt: Expose heartbeat interval " Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 21/27] drm/i915: Flush idle barriers when waiting Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 22/27] drm/i915: Allow userspace to specify ringsize on construction Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 23/27] drm/i915/gem: Honour O_NONBLOCK before throttling execbuf submissions Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 24/27] drm/i915/gt: Set unused mocs entry to follow PTE on tgl as on all others Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 14:13 ` Mika Kuoppala
2019-11-12 14:13 ` [Intel-gfx] " Mika Kuoppala
2019-11-12 14:39 ` Chris Wilson
2019-11-12 14:39 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 25/27] drm/i915/gt: Tidy up debug-warns for the mocs control table Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 26/27] drm/i915/gt: Refactor mocs loops into single control macro Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 17:02 ` Mika Kuoppala
2019-11-12 17:02 ` [Intel-gfx] " Mika Kuoppala
2019-11-12 18:12 ` Chris Wilson
2019-11-12 18:12 ` [Intel-gfx] " Chris Wilson
2019-11-12 9:28 ` [PATCH 27/27] drm/i915/selftests: Add coverage of mocs registers Chris Wilson
2019-11-12 9:28 ` [Intel-gfx] " Chris Wilson
2019-11-12 10:12 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/27] drm/i915: Flush context free work on cleanup Patchwork
2019-11-12 10:12 ` [Intel-gfx] " Patchwork
2019-11-12 10:23 ` Patchwork [this message]
2019-11-12 10:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2019-11-12 10:33 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-11-12 10:33 ` [Intel-gfx] " Patchwork
2019-11-12 14:23 ` [PATCH 01/27] " Mika Kuoppala
2019-11-12 14:23 ` [Intel-gfx] " Mika Kuoppala
2019-11-12 14:39 ` Chris Wilson
2019-11-12 14:39 ` [Intel-gfx] " 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=157355420512.31295.11013729633903200475@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.