All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [mlankhorst:locking-rework 26/27] drivers/gpu/drm/i915/i915_vma.c:1011:30: error: implicit declaration of function 'lockdep_is_held'
Date: Thu, 18 Jun 2020 15:49:01 +0800	[thread overview]
Message-ID: <202006181559.O2sT41qs%lkp@intel.com> (raw)

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

tree:   git://people.freedesktop.org/~mlankhorst/linux locking-rework
head:   500c1dc1795a3abb508252aef3fbbef0053f84d4
commit: 0be88c62774a10ec2522a9121affa316b9cb4b4b [26/27] drm/i915: Ensure we hold the pin mutex
config: x86_64-defconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 487ca07fcc75d52755c9fe2ee05bcb3b6eeeec44)
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
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        git checkout 0be88c62774a10ec2522a9121affa316b9cb4b4b
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross 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 >>):


vim +/lockdep_is_held +1011 drivers/gpu/drm/i915/i915_vma.c

  1002	
  1003	int i915_ggtt_pin(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,
  1004			  u32 align, unsigned int flags)
  1005	{
  1006		struct i915_address_space *vm = vma->vm;
  1007		int err;
  1008	
  1009		GEM_BUG_ON(!i915_vma_is_ggtt(vma));
  1010	
> 1011		WARN_ON(!ww && vma->resv && dma_resv_held(vma->resv));
  1012	
  1013		do {
  1014			if (ww)
  1015				err = i915_vma_pin_ww(vma, ww, 0, align, flags | PIN_GLOBAL);
  1016			else
  1017				err = i915_vma_pin(vma, 0, align, flags | PIN_GLOBAL);
  1018			if (err != -ENOSPC) {
  1019				if (!err) {
  1020					err = i915_vma_wait_for_bind(vma);
  1021					if (err)
  1022						i915_vma_unpin(vma);
  1023				}
  1024				return err;
  1025			}
  1026	
  1027			/* Unlike i915_vma_pin, we don't take no for an answer! */
  1028			flush_idle_contexts(vm->gt);
  1029			if (mutex_lock_interruptible(&vm->mutex) == 0) {
  1030				i915_gem_evict_vm(vm);
  1031				mutex_unlock(&vm->mutex);
  1032			}
  1033		} while (1);
  1034	}
  1035	

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

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

                 reply	other threads:[~2020-06-18  7:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202006181559.O2sT41qs%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.