From: kernel test robot <lkp@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
kbuild-all@lists.01.org, matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH 7/7] drm/i915: Use struct vma_resource instead of struct vma_snapshot
Date: Thu, 16 Dec 2021 02:50:56 +0800 [thread overview]
Message-ID: <202112160255.Kmo6u2NC-lkp@intel.com> (raw)
In-Reply-To: <20211215103611.777665-8-thomas.hellstrom@linux.intel.com>
Hi "Thomas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on next-20211214]
[cannot apply to drm-exynos/exynos-drm-next drm/drm-next drm-intel/for-linux-next v5.16-rc5]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Thomas-Hellstr-m/drm-i915-Asynchronous-vma-unbinding/20211215-183859
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: i386-randconfig-a003-20211214 (https://download.01.org/0day-ci/archive/20211216/202112160255.Kmo6u2NC-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/ede025870be746e37b5bcde123cdf741aa685fab
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Thomas-Hellstr-m/drm-i915-Asynchronous-vma-unbinding/20211215-183859
git checkout ede025870be746e37b5bcde123cdf741aa685fab
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/i915/i915_request.h:43,
from drivers/gpu/drm/i915/i915_active.h:13,
from drivers/gpu/drm/i915/gt/intel_ggtt_fencing.h:12,
from drivers/gpu/drm/i915/i915_vma.h:33,
from drivers/gpu/drm/i915/display/intel_display_types.h:50,
from drivers/gpu/drm/i915/i915_driver.c:51:
>> drivers/gpu/drm/i915/i915_vma_resource.h:176:15: warning: 'struct intel_memory_region' declared inside parameter list will not be visible outside of this definition or declaration
176 | struct intel_memory_region *mr,
| ^~~~~~~~~~~~~~~~~~~
--
In file included from drivers/gpu/drm/i915/i915_request.h:43,
from drivers/gpu/drm/i915/i915_active.h:13,
from drivers/gpu/drm/i915/gem/i915_gem_object_types.h:16,
from drivers/gpu/drm/i915/display/intel_frontbuffer.h:30,
from drivers/gpu/drm/i915/i915_drv.h:74,
from drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c:9:
>> drivers/gpu/drm/i915/i915_vma_resource.h:176:15: warning: 'struct intel_memory_region' declared inside parameter list will not be visible outside of this definition or declaration
176 | struct intel_memory_region *mr,
| ^~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c:464:5: warning: no previous prototype for 'prev_deps' [-Wmissing-prototypes]
464 | int prev_deps(struct ttm_buffer_object *bo, struct ttm_operation_ctx *ctx,
| ^~~~~~~~~
--
In file included from drivers/gpu/drm/i915/i915_request.h:43,
from drivers/gpu/drm/i915/i915_active.h:13,
from drivers/gpu/drm/i915/gem/i915_gem_object_types.h:16,
from drivers/gpu/drm/i915/display/intel_frontbuffer.h:30,
from drivers/gpu/drm/i915/i915_vma.c:28:
>> drivers/gpu/drm/i915/i915_vma_resource.h:176:15: warning: 'struct intel_memory_region' declared inside parameter list will not be visible outside of this definition or declaration
176 | struct intel_memory_region *mr,
| ^~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/i915_vma.c: In function 'i915_vma_resource_init_from_vma':
drivers/gpu/drm/i915/i915_vma.c:394:48: error: passing argument 8 of 'i915_vma_resource_init' from incompatible pointer type [-Werror=incompatible-pointer-types]
394 | i915_gem_object_is_lmem(obj), obj->mm.region,
| ~~~~~~~^~~~~~~
| |
| struct intel_memory_region *
In file included from drivers/gpu/drm/i915/i915_request.h:43,
from drivers/gpu/drm/i915/i915_active.h:13,
from drivers/gpu/drm/i915/gem/i915_gem_object_types.h:16,
from drivers/gpu/drm/i915/display/intel_frontbuffer.h:30,
from drivers/gpu/drm/i915/i915_vma.c:28:
drivers/gpu/drm/i915/i915_vma_resource.h:176:36: note: expected 'struct intel_memory_region *' but argument is of type 'struct intel_memory_region *'
176 | struct intel_memory_region *mr,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
cc1: some warnings being treated as errors
--
In file included from drivers/gpu/drm/i915/i915_request.h:43,
from drivers/gpu/drm/i915/i915_active.h:13,
from drivers/gpu/drm/i915/gem/i915_gem_object_types.h:16,
from drivers/gpu/drm/i915/display/intel_frontbuffer.h:30,
from drivers/gpu/drm/i915/i915_drv.h:74,
from drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c:12:
>> drivers/gpu/drm/i915/i915_vma_resource.h:176:15: warning: 'struct intel_memory_region' declared inside parameter list will not be visible outside of this definition or declaration
176 | struct intel_memory_region *mr,
| ^~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c:59:6: warning: no previous prototype for 'intel_pxp_debugfs_register' [-Wmissing-prototypes]
59 | void intel_pxp_debugfs_register(struct intel_pxp *pxp, struct dentry *gt_root)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +176 drivers/gpu/drm/i915/i915_vma_resource.h
146
147 /**
148 * i915_vma_resource_init - Initialize a vma resource.
149 * @vma_res: The vma resource to initialize
150 * @vm: Pointer to the vm.
151 * @pages: The pages sg-table.
152 * @page_sizes: Page sizes of the pages.
153 * @pages_rsgt: Pointer to a struct i915_refct_sgt of an object with
154 * delayed destruction.
155 * @readonly: Whether the vma should be bound read-only.
156 * @lmem: Whether the vma points to lmem.
157 * @mr: The memory region of the object the vma points to.
158 * @ops: The backend ops.
159 * @private: Bind backend private info.
160 * @start: Offset into the address space of bind range start.
161 * @node_size: Size of the allocated range manager node.
162 * @size: Bind size.
163 *
164 * Initializes a vma resource allocated using i915_vma_resource_alloc().
165 * The reason for having separate allocate and initialize function is that
166 * initialization may need to be performed from under a lock where
167 * allocation is not allowed.
168 */
169 static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res,
170 struct i915_address_space *vm,
171 struct sg_table *pages,
172 const struct i915_page_sizes *page_sizes,
173 struct i915_refct_sgt *pages_rsgt,
174 bool readonly,
175 bool lmem,
> 176 struct intel_memory_region *mr,
177 const struct i915_vma_ops *ops,
178 void *private,
179 unsigned long start,
180 unsigned long node_size,
181 unsigned long size)
182 {
183 __i915_vma_resource_init(vma_res);
184 vma_res->vm = vm;
185 vma_res->bi.pages = pages;
186 vma_res->bi.page_sizes = *page_sizes;
187 if (pages_rsgt)
188 vma_res->bi.pages_rsgt = i915_refct_sgt_get(pages_rsgt);
189 vma_res->bi.readonly = readonly;
190 vma_res->bi.lmem = lmem;
191 #if IS_ENABLED(CONFIG_DRM_I915_CAPTURE_ERROR)
192 vma_res->mr = mr;
193 #endif
194 vma_res->ops = ops;
195 vma_res->private = private;
196 vma_res->start = start;
197 vma_res->node_size = node_size;
198 vma_res->vma_size = size;
199 }
200
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-12-15 18:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 10:36 [Intel-gfx] [PATCH 0/7] drm/i915: Asynchronous vma unbinding Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 1/7] drm/i915: Avoid using the i915_fence_array when collecting dependencies Thomas Hellström
2021-12-15 17:08 ` kernel test robot
2021-12-15 17:49 ` kernel test robot
2021-12-16 11:06 ` [Intel-gfx] [RFC PATCH] drm/i915: prev_deps() can be static kernel test robot
2021-12-16 11:10 ` [Intel-gfx] [PATCH 1/7] drm/i915: Avoid using the i915_fence_array when collecting dependencies kernel test robot
2021-12-15 10:36 ` [Intel-gfx] [PATCH 2/7] drm/i915: Break out the i915_deps utility Thomas Hellström
2021-12-15 11:08 ` Jani Nikula
2021-12-15 10:36 ` [Intel-gfx] [PATCH 3/7] drm/i915: Require the vm mutex for i915_vma_bind() Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 4/7] drm/i915: Initial introduction of vma resources Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 5/7] drm/i915: Use the vma resource as argument for gtt binding / unbinding Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 6/7] drm/i915: Use vma resources for async unbinding Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 7/7] drm/i915: Use struct vma_resource instead of struct vma_snapshot Thomas Hellström
2021-12-15 15:56 ` kernel test robot
2021-12-15 18:50 ` kernel test robot [this message]
2021-12-15 11:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Asynchronous vma unbinding Patchwork
2021-12-15 11:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-15 12:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-15 14:19 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=202112160255.Kmo6u2NC-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
/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