[Intel-gfx] [PATCH] drm/i915: Call i915_sw_fence_fini on request cleanup

kbuild test robot lkp at intel.com
Thu Apr 11 13:50:23 UTC 2019

Hi Chris,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v5.1-rc4 next-20190410]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Call-i915_sw_fence_fini-on-request-cleanup/20190411-205947
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/gpu//drm/i915/i915_request.c: In function 'i915_fence_release':
>> drivers/gpu//drm/i915/i915_request.c:104:24: error: 'struct i915_request' has no member named 'semaphore'

vim +104 drivers/gpu//drm/i915/i915_request.c

    92	static void i915_fence_release(struct dma_fence *fence)
    93	{
    94		struct i915_request *rq = to_request(fence);
    96		/*
    97		 * The request is put onto a RCU freelist (i.e. the address
    98		 * is immediately reused), mark the fences as being freed now.
    99		 * Otherwise the debugobjects for the fences are only marked as
   100		 * freed when the slab cache itself is freed, and so we would get
   101		 * caught trying to reuse dead objects.
   102		 */
   103		i915_sw_fence_fini(&rq->submit);
 > 104		i915_sw_fence_fini(&rq->semaphore);
   106		kmem_cache_free(global.slab_requests, rq);
   107	}

0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 66349 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/intel-gfx/attachments/20190411/8e89b982/attachment-0001.gz>

More information about the Intel-gfx mailing list