[PATCH 4/7] drm/vmwgfx: use the new drm_exec object

kernel test robot lkp at intel.com
Sun Nov 17 09:15:49 UTC 2024


Hi Christian,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next linus/master drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip v6.12-rc7 next-20241115]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Christian-K-nig/drm-qxl-switch-to-using-drm_exec-v2/20241115-014610
base:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:    https://lore.kernel.org/r/20241114153020.6209-5-christian.koenig%40amd.com
patch subject: [PATCH 4/7] drm/vmwgfx: use the new drm_exec object
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20241117/202411171611.9LEZwWSe-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241117/202411171611.9LEZwWSe-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp at intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411171611.9LEZwWSe-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/vmwgfx/vmwgfx_validation.c:861: warning: Function parameter or struct member 'fence' not described in 'vmw_validation_bo_fence'


vim +861 drivers/gpu/drm/vmwgfx/vmwgfx_validation.c

   850	
   851	/**
   852	 * vmw_validation_bo_fence - Unreserve and fence buffer objects registered
   853	 * with a validation context
   854	 * @ctx: The validation context
   855	 *
   856	 * This function unreserves the buffer objects previously reserved using
   857	 * vmw_validation_bo_reserve, and fences them with a fence object.
   858	 */
   859	void vmw_validation_bo_fence(struct vmw_validation_context *ctx,
   860				     struct vmw_fence_obj *fence)
 > 861	{
   862		struct vmw_validation_bo_node *entry;
   863	
   864		list_for_each_entry(entry, &ctx->bo_list, base.head) {
   865			dma_resv_add_fence(entry->base.bo->base.resv, &fence->base,
   866					   DMA_RESV_USAGE_READ);
   867		}
   868		drm_exec_fini(&ctx->exec);
   869	}
   870	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


More information about the Intel-xe mailing list