public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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>,
	llvm@lists.linux.dev, kbuild-all@lists.01.org,
	matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH v4 1/6] drm/i915: Add support for moving fence waiting
Date: Sat, 20 Nov 2021 17:09:43 +0800	[thread overview]
Message-ID: <202111201727.QhQhXhrG-lkp@intel.com> (raw)
In-Reply-To: <20211118130230.154988-2-thomas.hellstrom@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3696 bytes --]

Hi "Thomas,

I love your patch! Yet something to improve:

[auto build test ERROR on drm-tip/drm-tip]
[also build test ERROR on drm-exynos/exynos-drm-next drm/drm-next v5.16-rc1 next-20211118]
[cannot apply to drm-intel/for-linux-next tegra-drm/drm/tegra/for-next airlied/drm-next]
[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-ttm-Async-migration/20211118-210436
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-randconfig-r001-20211118 (attached as .config)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/316dda0c6b91d043111cb348b43be6a6f2e3bb0a
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Thomas-Hellstr-m/drm-i915-ttm-Async-migration/20211118-210436
        git checkout 316dda0c6b91d043111cb348b43be6a6f2e3bb0a
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/i915/i915_vma.c:478:13: error: implicit declaration of function 'i915_vma_verify_bind_complete' [-Werror,-Wimplicit-function-declaration]
           GEM_BUG_ON(i915_vma_verify_bind_complete(vma));
                      ^
   1 error generated.


vim +/i915_vma_verify_bind_complete +478 drivers/gpu/drm/i915/i915_vma.c

   463	
   464	void __iomem *i915_vma_pin_iomap(struct i915_vma *vma)
   465	{
   466		void __iomem *ptr;
   467		int err;
   468	
   469		if (!i915_gem_object_is_lmem(vma->obj)) {
   470			if (GEM_WARN_ON(!i915_vma_is_map_and_fenceable(vma))) {
   471				err = -ENODEV;
   472				goto err;
   473			}
   474		}
   475	
   476		GEM_BUG_ON(!i915_vma_is_ggtt(vma));
   477		GEM_BUG_ON(!i915_vma_is_bound(vma, I915_VMA_GLOBAL_BIND));
 > 478		GEM_BUG_ON(i915_vma_verify_bind_complete(vma));
   479	
   480		ptr = READ_ONCE(vma->iomap);
   481		if (ptr == NULL) {
   482			/*
   483			 * TODO: consider just using i915_gem_object_pin_map() for lmem
   484			 * instead, which already supports mapping non-contiguous chunks
   485			 * of pages, that way we can also drop the
   486			 * I915_BO_ALLOC_CONTIGUOUS when allocating the object.
   487			 */
   488			if (i915_gem_object_is_lmem(vma->obj))
   489				ptr = i915_gem_object_lmem_io_map(vma->obj, 0,
   490								  vma->obj->base.size);
   491			else
   492				ptr = io_mapping_map_wc(&i915_vm_to_ggtt(vma->vm)->iomap,
   493							vma->node.start,
   494							vma->node.size);
   495			if (ptr == NULL) {
   496				err = -ENOMEM;
   497				goto err;
   498			}
   499	
   500			if (unlikely(cmpxchg(&vma->iomap, NULL, ptr))) {
   501				io_mapping_unmap(ptr);
   502				ptr = vma->iomap;
   503			}
   504		}
   505	
   506		__i915_vma_pin(vma);
   507	
   508		err = i915_vma_pin_fence(vma);
   509		if (err)
   510			goto err_unpin;
   511	
   512		i915_vma_set_ggtt_write(vma);
   513	
   514		/* NB Access through the GTT requires the device to be awake. */
   515		return ptr;
   516	
   517	err_unpin:
   518		__i915_vma_unpin(vma);
   519	err:
   520		return IO_ERR_PTR(err);
   521	}
   522	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35610 bytes --]

  parent reply	other threads:[~2021-11-20  9:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 13:02 [Intel-gfx] [PATCH v4 0/6] drm/i915/ttm: Async migration Thomas Hellström
2021-11-18 13:02 ` [Intel-gfx] [PATCH v4 1/6] drm/i915: Add support for moving fence waiting Thomas Hellström
2021-11-18 14:12   ` Matthew Auld
2021-11-20  9:09   ` kernel test robot [this message]
2021-11-18 13:02 ` [Intel-gfx] [PATCH v4 2/6] drm/i915/ttm: Move the i915_gem_obj_copy_ttm() function Thomas Hellström
2021-11-18 13:02 ` [Intel-gfx] [PATCH v4 3/6] drm/i915/ttm: Drop region reference counting Thomas Hellström
2021-11-18 14:19   ` Matthew Auld
2021-11-18 13:02 ` [Intel-gfx] [PATCH v4 4/6] drm/i915/ttm: Correctly handle waiting for gpu when shrinking Thomas Hellström
2021-11-18 14:30   ` Matthew Auld
2021-11-18 13:02 ` [Intel-gfx] [PATCH v4 5/6] drm/i915/ttm: Implement asynchronous TTM moves Thomas Hellström
2021-11-19 17:18   ` Matthew Auld
2021-11-18 13:02 ` [Intel-gfx] [PATCH v4 6/6] drm/i915/ttm: Update i915_gem_obj_copy_ttm() to be asynchronous Thomas Hellström
2021-11-19 17:22   ` Matthew Auld
2021-11-18 15:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev5) Patchwork
2021-11-18 15:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-19  5:34 ` [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=202111201727.QhQhXhrG-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=llvm@lists.linux.dev \
    --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