From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [RFC 3/8] drm/i915/svm: Introduce VM_BIND ioctl
Date: Sat, 25 Jan 2020 22:49:29 +0800 [thread overview]
Message-ID: <202001252255.ialzLvgN%lkp@intel.com> (raw)
In-Reply-To: <20200124085402.11644-4-niranjana.vishwanathapura@intel.com>
[-- Attachment #1: Type: text/plain, Size: 4472 bytes --]
Hi Niranjana,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip next-20200124]
[cannot apply to v5.5-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Niranjana-Vishwanathapura/drm-i915-svm-WIP-SVM-runtime-allocator-support/20200125-144343
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-g003-20200125 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/i915/display/intel_display_types.h:46:0,
from drivers/gpu/drm/i915/display/intel_combo_phy.c:7:
drivers/gpu/drm/i915/i915_drv.h: In function '__i915_gem_address_space_lookup_rcu':
>> drivers/gpu/drm/i915/i915_drv.h:1924:30: error: 'struct drm_i915_file_private' has no member named 'vm_idr'; did you mean 'vm_xa'?
return idr_find(&file_priv->vm_idr, id);
^~~~~~
vm_xa
--
In file included from drivers/gpu/drm/i915/selftests/igt_reset.c:12:0:
drivers/gpu/drm/i915/selftests/../i915_drv.h: In function '__i915_gem_address_space_lookup_rcu':
>> drivers/gpu/drm/i915/selftests/../i915_drv.h:1924:30: error: 'struct drm_i915_file_private' has no member named 'vm_idr'; did you mean 'vm_xa'?
return idr_find(&file_priv->vm_idr, id);
^~~~~~
vm_xa
--
/dev/null:1:0: error: cannot open /dev/null.gcno
In file included from drivers/gpu/drm/i915/display/intel_display_types.h:46:0,
from <command-line>:0:
drivers/gpu/drm/i915/i915_drv.h: In function '__i915_gem_address_space_lookup_rcu':
>> drivers/gpu/drm/i915/i915_drv.h:1924:30: error: 'struct drm_i915_file_private' has no member named 'vm_idr'; did you mean 'vm_xa'?
return idr_find(&file_priv->vm_idr, id);
^~~~~~
vm_xa
--
In file included from drivers/gpu/drm/i915/display/intel_display_types.h:46:0,
from drivers/gpu/drm/i915/i915_drv.c:53:
drivers/gpu/drm/i915/i915_drv.h: In function '__i915_gem_address_space_lookup_rcu':
>> drivers/gpu/drm/i915/i915_drv.h:1924:30: error: 'struct drm_i915_file_private' has no member named 'vm_idr'; did you mean 'vm_xa'?
return idr_find(&file_priv->vm_idr, id);
^~~~~~
vm_xa
drivers/gpu/drm/i915/i915_drv.h:1925:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
cc1: all warnings being treated as errors
--
In file included from drivers/gpu/drm/i915/gt/intel_lrc.c:136:0:
drivers/gpu/drm/i915/i915_drv.h: In function '__i915_gem_address_space_lookup_rcu':
>> drivers/gpu/drm/i915/i915_drv.h:1924:30: error: 'struct drm_i915_file_private' has no member named 'vm_idr'; did you mean 'vm_xa'?
return idr_find(&file_priv->vm_idr, id);
^~~~~~
vm_xa
drivers/gpu/drm/i915/gt/intel_lrc.c: In function 'execlists_capture_work':
drivers/gpu/drm/i915/gt/intel_lrc.c:2559:2: error: implicit declaration of function 'i915_gpu_coredump_put'; did you mean 'i915_gpu_coredump_alloc'? [-Werror=implicit-function-declaration]
i915_gpu_coredump_put(cap->error);
^~~~~~~~~~~~~~~~~~~~~
i915_gpu_coredump_alloc
cc1: all warnings being treated as errors
vim +1924 drivers/gpu/drm/i915/i915_drv.h
1919
1920 static inline struct i915_address_space *
1921 __i915_gem_address_space_lookup_rcu(struct drm_i915_file_private *file_priv,
1922 u32 id)
1923 {
> 1924 return idr_find(&file_priv->vm_idr, id);
1925 }
1926
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35894 bytes --]
next prev parent reply other threads:[~2020-01-25 14:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 8:53 [Intel-gfx] [RFC 0/8] drm/i915/svm: [WIP] SVM runtime allocator support Niranjana Vishwanathapura
2020-01-24 8:53 ` [Intel-gfx] [RFC 1/8] drm/i915/svm: Support partial binding in ppgtt Niranjana Vishwanathapura
2020-01-24 8:53 ` [Intel-gfx] [RFC 2/8] drm/i915/svm: Add support to mark VMs as active Niranjana Vishwanathapura
2020-01-24 8:53 ` [Intel-gfx] [RFC 3/8] drm/i915/svm: Introduce VM_BIND ioctl Niranjana Vishwanathapura
2020-01-25 14:49 ` kbuild test robot [this message]
2020-01-26 7:35 ` kbuild test robot
2020-01-24 8:53 ` [Intel-gfx] [RFC 4/8] drm/i915/svm: Manage SVM bindings added using VM_BIND Niranjana Vishwanathapura
2020-01-24 8:53 ` [Intel-gfx] [RFC 5/8] drm/i915/svm: Handle persistent vmas Niranjana Vishwanathapura
2020-01-24 8:54 ` [Intel-gfx] [RFC 6/8] drm/i915/svm: Skip vma_lookup for " Niranjana Vishwanathapura
2020-01-24 8:54 ` [Intel-gfx] [RFC 7/8] drm/i915/svm: Add support to en/disable SVM Niranjana Vishwanathapura
2020-01-25 16:40 ` kbuild test robot
2020-01-24 8:54 ` [Intel-gfx] [RFC 8/8] drm/i915/svm: VM_BIND for endless batch buffer Niranjana Vishwanathapura
2020-01-24 9:54 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/svm: [WIP] SVM runtime allocator support Patchwork
2020-01-24 18:54 ` [Intel-gfx] [RFC 0/8] " Niranjana Vishwanathapura
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=202001252255.ialzLvgN%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.