All of lore.kernel.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: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/20] drm/i915: Preallocate stashes for vma page-directories
Date: Mon, 06 Jul 2020 06:28:08 -0000	[thread overview]
Message-ID: <159401688836.17683.16409178541736603513@emeril.freedesktop.org> (raw)
In-Reply-To: <20200706061926.6687-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [01/20] drm/i915: Preallocate stashes for vma page-directories
URL   : https://patchwork.freedesktop.org/series/79129/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
b5c5d0ce6d3d drm/i915: Preallocate stashes for vma page-directories
5ff5ae1fb079 drm/i915: Switch to object allocations for page directories
1da308be5b55 drm/i915/gem: Don't drop the timeline lock during execbuf
a8aa1e74f47e drm/i915/gem: Rename execbuf.bind_link to unbound_link
6779fcaed114 drm/i915/gem: Break apart the early i915_vma_pin from execbuf object lookup
c3cc3ce10691 drm/i915/gem: Remove the call for no-evict i915_vma_pin
acb85ac92a2f drm/i915: Add list_for_each_entry_safe_continue_reverse
-:21: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'pos' - possible side-effects?
#21: FILE: drivers/gpu/drm/i915/i915_utils.h:269:
+#define list_for_each_entry_safe_continue_reverse(pos, n, head, member)	\
+	for (pos = list_prev_entry(pos, member),			\
+	     n = list_prev_entry(pos, member);				\
+	     &pos->member != (head);					\
+	     pos = n, n = list_prev_entry(n, member))

-:21: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'n' - possible side-effects?
#21: FILE: drivers/gpu/drm/i915/i915_utils.h:269:
+#define list_for_each_entry_safe_continue_reverse(pos, n, head, member)	\
+	for (pos = list_prev_entry(pos, member),			\
+	     n = list_prev_entry(pos, member);				\
+	     &pos->member != (head);					\
+	     pos = n, n = list_prev_entry(n, member))

-:21: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'member' - possible side-effects?
#21: FILE: drivers/gpu/drm/i915/i915_utils.h:269:
+#define list_for_each_entry_safe_continue_reverse(pos, n, head, member)	\
+	for (pos = list_prev_entry(pos, member),			\
+	     n = list_prev_entry(pos, member);				\
+	     &pos->member != (head);					\
+	     pos = n, n = list_prev_entry(n, member))

total: 0 errors, 0 warnings, 3 checks, 12 lines checked
ed90e5840625 drm/i915: Always defer fenced work to the worker
03e637530b30 drm/i915/gem: Assign context id for async work
fe694efd1728 drm/i915: Export a preallocate variant of i915_active_acquire()
8669de2e382e drm/i915/gem: Separate the ww_mutex walker into its own list
a1fb11db685d drm/i915/gem: Asynchronous GTT unbinding
92aa37aeda01 drm/i915/gem: Bind the fence async for execbuf
6002974eb6ce drm/i915/gem: Include cmdparser in common execbuf pinning
8b519af3185f drm/i915/gem: Include secure batch in common execbuf pinning
3a96506f63d3 drm/i915/gem: Reintroduce multiple passes for reloc processing
-:1434: WARNING:MEMORY_BARRIER: memory barrier without comment
#1434: FILE: drivers/gpu/drm/i915/gem/selftests/i915_gem_execbuffer.c:161:
+		wmb();

total: 0 errors, 1 warnings, 0 checks, 1421 lines checked
2036c3ef6f3e drm/i915: Add an implementation for i915_gem_ww_ctx locking, v2.
-:59: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#59: 
new file mode 100644

-:354: WARNING:LINE_SPACING: Missing a blank line after declarations
#354: FILE: drivers/gpu/drm/i915/mm/st_acquire_ctx.c:106:
+	const unsigned int total = ARRAY_SIZE(dl->obj);
+	I915_RND_STATE(prng);

-:450: WARNING:YIELD: Using yield() is generally wrong. See yield() kernel-doc (sched/core.c)
#450: FILE: drivers/gpu/drm/i915/mm/st_acquire_ctx.c:202:
+	yield(); /* start all threads before we begin */

total: 0 errors, 3 warnings, 0 checks, 446 lines checked
0c763806ba4f drm/i915/gem: Pull execbuf dma resv under a single critical section
f3622825131d drm/i915/gem: Replace i915_gem_object.mm.mutex with reservation_ww_class
33bcfafbc4ab drm/i915: Track i915_vma with its own reference counter
-:2081: CHECK:UNCOMMENTED_DEFINITION: spinlock_t definition without comment
#2081: FILE: drivers/gpu/drm/i915/gt/intel_gtt.h:254:
+		spinlock_t lock;

-:3963: CHECK:UNCOMMENTED_DEFINITION: spinlock_t definition without comment
#3963: FILE: drivers/gpu/drm/i915/i915_vma.h:392:
+	spinlock_t lock;

-:4210: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4210: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:419:
+						if (offset < hole_start + vma->size)

-:4221: WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#4221: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:427:
+						       __func__, p->name, err, npages, prime, offset,

-:4231: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4231: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:444:
+						if (offset + vma->node.size > hole_end)

-:4247: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4247: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:453:
+						if (offset < hole_start + vma->node.size)

-:4259: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4259: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:476:
+						if (offset + vma->node.size > hole_end)

-:4275: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4275: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:485:
+						if (offset < hole_start + vma->node.size)

-:4287: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4287: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:509:
+						if (offset + vma->size >= hole_end)

-:4303: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4303: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:518:
+						if (offset < hole_start + vma->size)

-:4315: WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#4315: FILE: drivers/gpu/drm/i915/selftests/i915_gem_gtt.c:541:
+						if (offset + vma->size >= hole_end)

total: 0 errors, 9 warnings, 2 checks, 4801 lines checked

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

  parent reply	other threads:[~2020-07-06  6:28 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06  6:19 [Intel-gfx] s/obj->mm.lock// Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 01/20] drm/i915: Preallocate stashes for vma page-directories Chris Wilson
2020-07-06 18:15   ` Matthew Auld
2020-07-06 18:20     ` Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 02/20] drm/i915: Switch to object allocations for page directories Chris Wilson
2020-07-06 19:06   ` Matthew Auld
2020-07-06 19:31     ` Chris Wilson
2020-07-06 20:01     ` Chris Wilson
2020-07-06 21:08       ` Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 03/20] drm/i915/gem: Don't drop the timeline lock during execbuf Chris Wilson
2020-07-08 16:54   ` Tvrtko Ursulin
2020-07-08 18:08     ` Chris Wilson
2020-07-09 10:52       ` Tvrtko Ursulin
2020-07-09 10:57         ` Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 04/20] drm/i915/gem: Rename execbuf.bind_link to unbound_link Chris Wilson
2020-07-10 11:26   ` Tvrtko Ursulin
2020-07-06  6:19 ` [Intel-gfx] [PATCH 05/20] drm/i915/gem: Break apart the early i915_vma_pin from execbuf object lookup Chris Wilson
2020-07-10 11:27   ` Tvrtko Ursulin
2020-07-06  6:19 ` [Intel-gfx] [PATCH 06/20] drm/i915/gem: Remove the call for no-evict i915_vma_pin Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 07/20] drm/i915: Add list_for_each_entry_safe_continue_reverse Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 08/20] drm/i915: Always defer fenced work to the worker Chris Wilson
2020-07-08 12:18   ` Tvrtko Ursulin
2020-07-08 12:25     ` Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 09/20] drm/i915/gem: Assign context id for async work Chris Wilson
2020-07-08 12:26   ` Tvrtko Ursulin
2020-07-08 12:42     ` Chris Wilson
2020-07-08 14:24       ` Tvrtko Ursulin
2020-07-08 15:36         ` Chris Wilson
2020-07-09 11:01           ` Tvrtko Ursulin
2020-07-09 11:07             ` Chris Wilson
2020-07-09 11:59               ` Tvrtko Ursulin
2020-07-09 12:07                 ` Chris Wilson
2020-07-13 12:22                   ` Tvrtko Ursulin
2020-07-14 14:01                     ` Chris Wilson
2020-07-08 12:45     ` Tvrtko Ursulin
2020-07-06  6:19 ` [Intel-gfx] [PATCH 10/20] drm/i915: Export a preallocate variant of i915_active_acquire() Chris Wilson
2020-07-09 14:36   ` Maarten Lankhorst
2020-07-10 12:24     ` Tvrtko Ursulin
2020-07-10 12:32       ` Maarten Lankhorst
2020-07-13 14:29   ` Tvrtko Ursulin
2020-07-06  6:19 ` [Intel-gfx] [PATCH 11/20] drm/i915/gem: Separate the ww_mutex walker into its own list Chris Wilson
2020-07-13 14:53   ` Tvrtko Ursulin
2020-07-14 14:10     ` Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 12/20] drm/i915/gem: Asynchronous GTT unbinding Chris Wilson
2020-07-14  9:02   ` Tvrtko Ursulin
2020-07-14 15:05     ` Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 13/20] drm/i915/gem: Bind the fence async for execbuf Chris Wilson
2020-07-14 12:19   ` Tvrtko Ursulin
2020-07-14 15:21     ` Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 14/20] drm/i915/gem: Include cmdparser in common execbuf pinning Chris Wilson
2020-07-14 12:48   ` Tvrtko Ursulin
2020-07-06  6:19 ` [Intel-gfx] [PATCH 15/20] drm/i915/gem: Include secure batch " Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 16/20] drm/i915/gem: Reintroduce multiple passes for reloc processing Chris Wilson
2020-07-09 15:39   ` Tvrtko Ursulin
2020-07-06  6:19 ` [Intel-gfx] [PATCH 17/20] drm/i915: Add an implementation for i915_gem_ww_ctx locking, v2 Chris Wilson
2020-07-06 17:21   ` kernel test robot
2020-07-06  6:19 ` [Intel-gfx] [PATCH 18/20] drm/i915/gem: Pull execbuf dma resv under a single critical section Chris Wilson
2020-07-06  6:19 ` [Intel-gfx] [PATCH 19/20] drm/i915/gem: Replace i915_gem_object.mm.mutex with reservation_ww_class Chris Wilson
2020-07-09 14:06   ` Maarten Lankhorst
2020-07-06  6:19 ` [Intel-gfx] [PATCH 20/20] drm/i915: Track i915_vma with its own reference counter Chris Wilson
2020-07-06  6:28 ` Patchwork [this message]
2020-07-06  6:29 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [01/20] drm/i915: Preallocate stashes for vma page-directories Patchwork
2020-07-06  6:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-06  7:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-07-27 18:53 ` [Intel-gfx] s/obj->mm.lock// Thomas Hellström (Intel)

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=159401688836.17683.16409178541736603513@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.