All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for implicit fencing/dma-resv rules for shared buffers
Date: Tue, 22 Jun 2021 17:11:08 -0000	[thread overview]
Message-ID: <162438186829.30777.9358255163136027337@emeril.freedesktop.org> (raw)
In-Reply-To: <20210622165511.3169559-1-daniel.vetter@ffwll.ch>

== Series Details ==

Series: implicit fencing/dma-resv rules for shared buffers
URL   : https://patchwork.freedesktop.org/series/91789/
State : warning

== Summary ==

$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+drivers/gpu/drm/i915/display/intel_display.c:1893:21:    expected struct i915_vma *[assigned] vma
+drivers/gpu/drm/i915/display/intel_display.c:1893:21:    got void [noderef] __iomem *[assigned] iomem
+drivers/gpu/drm/i915/display/intel_display.c:1893:21: warning: incorrect type in assignment (different address spaces)
+drivers/gpu/drm/i915/gem/i915_gem_ttm.c:733:38: warning: symbol 'i915_gem_ttm_obj_ops' was not declared. Should it be static?
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:27:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:27:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:27:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:32:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:32:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:49:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:49:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:49:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:56:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:56:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_reset.c:1396:5: warning: context imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block
+drivers/gpu/drm/i915/gt/intel_ring_submission.c:1207:24: warning: Using plain integer as NULL pointer
+drivers/gpu/drm/i915/i915_perf.c:1434:15: warning: memset with byte count of 16777216
+drivers/gpu/drm/i915/i915_perf.c:1488:15: warning: memset with byte count of 16777216
+drivers/gpu/drm/selftests/test-drm_damage_helper.c:244:25: warning: Using plain integer as NULL pointer
+drivers/gpu/drm/selftests/test-drm_damage_helper.c:268:23: warning: Using plain integer as NULL pointer
+drivers/gpu/drm/ttm/ttm_bo.c:1157:9: warning: context imbalance in 'ttm_bo_swapout' - unexpected unlock
+drivers/gpu/drm/ttm/ttm_bo.c:309:28: warning: context imbalance in 'ttm_bo_cleanup_refs' - unexpected unlock
+drivers/gpu/drm/ttm/ttm_bo.c:367:27: warning: context imbalance in 'ttm_bo_delayed_delete' - different lock contexts for basic block
+drivers/gpu/drm/ttm/ttm_bo.c:633:5: warning: context imbalance in 'ttm_mem_evict_first' - wrong count at exit
+drivers/gpu/drm/ttm/ttm_bo_util.c:281:38:    expected void *virtual
+drivers/gpu/drm/ttm/ttm_bo_util.c:281:38:    got void [noderef] __iomem *
+drivers/gpu/drm/ttm/ttm_bo_util.c:281:38: warning: incorrect type in assignment (different address spaces)
+drivers/gpu/drm/ttm/ttm_bo_util.c:284:38:    expected void *virtual
+drivers/gpu/drm/ttm/ttm_bo_util.c:284:38:    got void [noderef] __iomem *
+drivers/gpu/drm/ttm/ttm_bo_util.c:284:38: warning: incorrect type in assignment (different address spaces)
+drivers/gpu/drm/ttm/ttm_bo_util.c:287:38:    expected void *virtual
+drivers/gpu/drm/ttm/ttm_bo_util.c:287:38:    got void [noderef] __iomem *
+drivers/gpu/drm/ttm/ttm_bo_util.c:287:38: warning: incorrect type in assignment (different address spaces)
+drivers/gpu/drm/ttm/ttm_bo_util.c:367:28:    expected void volatile [noderef] __iomem *addr
+drivers/gpu/drm/ttm/ttm_bo_util.c:367:28:    got void *virtual
+drivers/gpu/drm/ttm/ttm_bo_util.c:367:28: warning: incorrect type in argument 1 (different address spaces)
+drivers/gpu/drm/ttm/ttm_device.c:130:5: warning: context imbalance in 'ttm_device_swapout' - wrong count at exit
+./include/asm-generic/bitops/find.h:112:45: warning: shift count is negative (-262080)
+./include/asm-generic/bitops/find.h:32:31: warning: shift count is negative (-262080)
+./include/linux/seqlock.h:840:24: warning: trying to copy expression type 31
+./include/linux/seqlock.h:840:24: warning: trying to copy expression type 31
+./include/linux/seqlock.h:866:16: warning: trying to copy expression type 31
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read64' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_read8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'fwtable_write8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read64' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_read8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen11_fwtable_write8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read64' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_read8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen12_fwtable_write8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read64' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_read8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen6_write8' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write16' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write32' - different lock contexts for basic block
+./include/linux/spinlock.h:409:9: warning: context imbalance in 'gen8_write8' - different lock contexts for basic block


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

  parent reply	other threads:[~2021-06-22 17:11 UTC|newest]

Thread overview: 175+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 16:54 [PATCH 00/15] implicit fencing/dma-resv rules for shared buffers Daniel Vetter
2021-06-22 16:54 ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:54 ` [PATCH 01/15] dma-resv: Fix kerneldoc Daniel Vetter
2021-06-22 16:54   ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:54   ` Daniel Vetter
2021-06-22 18:19   ` Alex Deucher
2021-06-22 18:19     ` [Intel-gfx] " Alex Deucher
2021-06-22 18:19     ` Alex Deucher
2021-06-22 18:49   ` Sam Ravnborg
2021-06-22 18:49     ` [Intel-gfx] " Sam Ravnborg
2021-06-22 19:19     ` Daniel Vetter
2021-06-22 19:19       ` [Intel-gfx] " Daniel Vetter
2021-06-22 19:19       ` Daniel Vetter
2021-06-23  8:31   ` Christian König
2021-06-23  8:31     ` [Intel-gfx] " Christian König
2021-06-23  8:31     ` Christian König
2021-06-23 15:15     ` Daniel Vetter
2021-06-23 15:15       ` [Intel-gfx] " Daniel Vetter
2021-06-23 15:15       ` Daniel Vetter
2021-06-22 16:54 ` [PATCH 02/15] dma-buf: Switch to inline kerneldoc Daniel Vetter
2021-06-22 16:54   ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:54   ` Daniel Vetter
2021-06-22 18:24   ` Alex Deucher
2021-06-22 18:24     ` [Intel-gfx] " Alex Deucher
2021-06-22 18:24     ` Alex Deucher
2021-06-22 19:01   ` Sam Ravnborg
2021-06-22 19:01     ` [Intel-gfx] " Sam Ravnborg
2021-06-22 19:21     ` Daniel Vetter
2021-06-22 19:21       ` [Intel-gfx] " Daniel Vetter
2021-06-22 19:21       ` Daniel Vetter
2021-06-23  8:32   ` Christian König
2021-06-23  8:32     ` [Intel-gfx] " Christian König
2021-06-23  8:32     ` Christian König
2021-06-23 16:17   ` [PATCH] " Daniel Vetter
2021-06-23 16:17     ` [Intel-gfx] " Daniel Vetter
2021-06-23 16:17     ` Daniel Vetter
2021-06-23 17:33     ` Sam Ravnborg
2021-06-23 17:33       ` [Intel-gfx] " Sam Ravnborg
2021-06-22 16:54 ` [PATCH 03/15] dma-buf: Document dma-buf implicit fencing/resv fencing rules Daniel Vetter
2021-06-22 16:54   ` [Intel-gfx] " Daniel Vetter
2021-06-23  8:41   ` Christian König
2021-06-23  8:41     ` [Intel-gfx] " Christian König
2021-06-23 16:19   ` [PATCH] " Daniel Vetter
2021-06-23 16:19     ` [Intel-gfx] " Daniel Vetter
2021-06-24  6:59     ` Dave Airlie
2021-06-24  6:59       ` [Intel-gfx] " Dave Airlie
2021-06-24 11:08     ` [Mesa-dev] " Daniel Stone
2021-06-24 11:08       ` [Intel-gfx] " Daniel Stone
2021-06-24 11:23       ` Daniel Vetter
2021-06-24 11:23         ` [Intel-gfx] " Daniel Vetter
2021-06-24 12:48     ` Daniel Vetter
2021-06-24 12:52     ` Daniel Vetter
2021-06-22 16:55 ` [PATCH 04/15] drm/panfrost: Shrink sched_lock Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-23 16:52   ` Boris Brezillon
2021-06-23 16:52     ` [Intel-gfx] " Boris Brezillon
2021-06-22 16:55 ` [PATCH 05/15] drm/panfrost: Use xarray and helpers for depedency tracking Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-23 16:51   ` Boris Brezillon
2021-06-23 16:51     ` [Intel-gfx] " Boris Brezillon
2021-06-23 16:51     ` Boris Brezillon
2021-06-22 16:55 ` [PATCH 06/15] drm/panfrost: Fix implicit sync Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-23 16:47   ` Boris Brezillon
2021-06-23 16:47     ` [Intel-gfx] " Boris Brezillon
2021-06-23 16:47     ` Boris Brezillon
2021-06-23 19:17     ` Daniel Vetter
2021-06-23 19:17       ` [Intel-gfx] " Daniel Vetter
2021-06-23 19:17       ` Daniel Vetter
2021-06-22 16:55 ` [PATCH 07/15] drm/atomic-helper: make drm_gem_plane_helper_prepare_fb the default Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 19:10   ` Sam Ravnborg
2021-06-22 19:10     ` [Intel-gfx] " Sam Ravnborg
2021-06-22 20:20     ` Daniel Vetter
2021-06-22 20:20       ` [Intel-gfx] " Daniel Vetter
2021-06-23 15:39       ` Sam Ravnborg
2021-06-23 15:39         ` [Intel-gfx] " Sam Ravnborg
2021-06-23 16:22   ` [PATCH] " Daniel Vetter
2021-06-23 16:22     ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:55 ` [PATCH 08/15] drm/<driver>: drm_gem_plane_helper_prepare_fb is now " Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-24  8:32   ` Philipp Zabel
2021-06-24  8:32     ` Philipp Zabel
2021-06-24  8:32     ` [Intel-gfx] " Philipp Zabel
2021-06-24  8:32     ` Philipp Zabel
2021-06-24  8:32     ` Philipp Zabel
2021-06-24  8:32     ` Philipp Zabel
2021-06-24  8:32     ` Philipp Zabel
2021-06-24  8:32     ` Philipp Zabel
2021-06-22 16:55 ` [PATCH 09/15] drm/armada: Remove prepare/cleanup_fb hooks Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-24 12:46   ` Maxime Ripard
2021-06-24 12:46     ` [Intel-gfx] " Maxime Ripard
2021-06-22 16:55 ` [PATCH 10/15] drm/vram-helpers: Create DRM_GEM_VRAM_PLANE_HELPER_FUNCS Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-24  7:38   ` Thomas Zimmermann
2021-06-24  7:38     ` [Intel-gfx] " Thomas Zimmermann
2021-06-24  7:46   ` Thomas Zimmermann
2021-06-24  7:46     ` [Intel-gfx] " Thomas Zimmermann
2021-06-24 13:39     ` Daniel Vetter
2021-06-24 13:39       ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:55 ` [PATCH 11/15] drm/omap: Follow implicit fencing in prepare_fb Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:55 ` [PATCH 12/15] drm/simple-helper: drm_gem_simple_display_pipe_prepare_fb as default Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 19:15   ` Sam Ravnborg
2021-06-22 19:15     ` [Intel-gfx] " Sam Ravnborg
2021-06-23 16:24   ` [PATCH] " Daniel Vetter
2021-06-23 16:24     ` [Intel-gfx] " Daniel Vetter
2021-06-23 17:34     ` Sam Ravnborg
2021-06-23 17:34       ` [Intel-gfx] " Sam Ravnborg
2021-06-22 16:55 ` [PATCH 13/15] drm/tiny: drm_gem_simple_display_pipe_prepare_fb is the default Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 16:55   ` Daniel Vetter
2021-06-22 16:55 ` [PATCH 14/15] drm/gem: Tiny kernel clarification for drm_gem_fence_array_add Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-23  8:42   ` Christian König
2021-06-23  8:42     ` [Intel-gfx] " Christian König
2021-06-24 12:41     ` Daniel Vetter
2021-06-24 12:41       ` [Intel-gfx] " Daniel Vetter
2021-06-24 12:48       ` Christian König
2021-06-24 12:48         ` [Intel-gfx] " Christian König
2021-06-24 13:32         ` Daniel Vetter
2021-06-24 13:32           ` [Intel-gfx] " Daniel Vetter
2021-06-24 13:35           ` Christian König
2021-06-24 13:35             ` [Intel-gfx] " Christian König
2021-06-24 13:41             ` Daniel Vetter
2021-06-24 13:41               ` [Intel-gfx] " Daniel Vetter
2021-06-24 13:45               ` Christian König
2021-06-24 13:45                 ` [Intel-gfx] " Christian König
2021-06-22 16:55 ` [PATCH 15/15] RFC: drm/amdgpu: Implement a proper implicit fencing uapi Daniel Vetter
2021-06-22 16:55   ` [Intel-gfx] " Daniel Vetter
2021-06-22 23:56   ` kernel test robot
2021-06-23  9:45   ` Bas Nieuwenhuizen
2021-06-23  9:45     ` [Intel-gfx] " Bas Nieuwenhuizen
2021-06-23 12:18     ` Daniel Vetter
2021-06-23 12:18       ` [Intel-gfx] " Daniel Vetter
2021-06-23 12:59       ` Christian König
2021-06-23 12:59         ` [Intel-gfx] " Christian König
2021-06-23 13:38         ` Bas Nieuwenhuizen
2021-06-23 13:38           ` [Intel-gfx] " Bas Nieuwenhuizen
2021-06-23 13:44           ` Christian König
2021-06-23 13:44             ` [Intel-gfx] " Christian König
2021-06-23 13:49             ` Daniel Vetter
2021-06-23 13:49               ` [Intel-gfx] " Daniel Vetter
2021-06-23 14:02               ` Christian König
2021-06-23 14:02                 ` [Intel-gfx] " Christian König
2021-06-23 14:50                 ` Daniel Vetter
2021-06-23 14:50                   ` [Intel-gfx] " Daniel Vetter
2021-06-23 14:58                   ` Bas Nieuwenhuizen
2021-06-23 14:58                     ` [Intel-gfx] " Bas Nieuwenhuizen
2021-06-23 15:03                     ` Daniel Vetter
2021-06-23 15:03                       ` [Intel-gfx] " Daniel Vetter
2021-06-23 15:07                       ` Christian König
2021-06-23 15:07                         ` [Intel-gfx] " Christian König
2021-06-23 15:12                         ` Daniel Vetter
2021-06-23 15:12                           ` [Intel-gfx] " Daniel Vetter
2021-06-23 15:15                           ` Christian König
2021-06-23 15:15                             ` [Intel-gfx] " Christian König
2021-06-22 17:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for implicit fencing/dma-resv rules for shared buffers Patchwork
2021-06-22 17:11 ` Patchwork [this message]
2021-06-22 17:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-22 19:12 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-23 17:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for implicit fencing/dma-resv rules for shared buffers (rev5) Patchwork
2021-06-23 17:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-06-23 17:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-23 21:04 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=162438186829.30777.9358255163136027337@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=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 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.