From: kernel test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
dri-devel@lists.freedesktop.org,
"Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Dafna Hirschfeld" <dafna.hirschfeld@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>
Subject: Re: [PATCH v5 7/8] drm/xe/userptr: replace xe_hmm with gpusvm
Date: Tue, 19 Aug 2025 08:18:23 +0800 [thread overview]
Message-ID: <202508190722.CIuroUt0-lkp@intel.com> (raw)
In-Reply-To: <20250818152152.67815-17-matthew.auld@intel.com>
Hi Matthew,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on next-20250818]
[cannot apply to drm-exynos/exynos-drm-next linus/master v6.17-rc2]
[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/Matthew-Auld/drm-gpusvm-fix-hmm_pfn_to_map_order-usage/20250818-232336
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20250818152152.67815-17-matthew.auld%40intel.com
patch subject: [PATCH v5 7/8] drm/xe/userptr: replace xe_hmm with gpusvm
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250819/202508190722.CIuroUt0-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250819/202508190722.CIuroUt0-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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202508190722.CIuroUt0-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/xe/xe_userptr.c:177:24: error: no member named 'notifier_seq' in 'struct xe_userptr'
177 | uvma->userptr.notifier_seq))
| ~~~~~~~~~~~~~ ^
drivers/gpu/drm/xe/xe_userptr.c:178:17: error: no member named 'notifier_seq' in 'struct xe_userptr'
178 | uvma->userptr.notifier_seq -= 2;
| ~~~~~~~~~~~~~ ^
2 errors generated.
vim +177 drivers/gpu/drm/xe/xe_userptr.c
0bab17b0664f42 Matthew Auld 2025-08-18 154
0bab17b0664f42 Matthew Auld 2025-08-18 155 #if IS_ENABLED(CONFIG_DRM_XE_USERPTR_INVAL_INJECT)
0bab17b0664f42 Matthew Auld 2025-08-18 156 /**
0bab17b0664f42 Matthew Auld 2025-08-18 157 * xe_vma_userptr_force_invalidate() - force invalidate a userptr
0bab17b0664f42 Matthew Auld 2025-08-18 158 * @uvma: The userptr vma to invalidate
0bab17b0664f42 Matthew Auld 2025-08-18 159 *
0bab17b0664f42 Matthew Auld 2025-08-18 160 * Perform a forced userptr invalidation for testing purposes.
0bab17b0664f42 Matthew Auld 2025-08-18 161 */
0bab17b0664f42 Matthew Auld 2025-08-18 162 void xe_vma_userptr_force_invalidate(struct xe_userptr_vma *uvma)
0bab17b0664f42 Matthew Auld 2025-08-18 163 {
0bab17b0664f42 Matthew Auld 2025-08-18 164 struct xe_vm *vm = xe_vma_vm(&uvma->vma);
0bab17b0664f42 Matthew Auld 2025-08-18 165
0bab17b0664f42 Matthew Auld 2025-08-18 166 /* Protect against concurrent userptr pinning */
0bab17b0664f42 Matthew Auld 2025-08-18 167 lockdep_assert_held(&vm->lock);
0bab17b0664f42 Matthew Auld 2025-08-18 168 /* Protect against concurrent notifiers */
97df487309a7ce Matthew Auld 2025-08-18 169 lockdep_assert_held(&vm->svm.gpusvm.notifier_lock);
0bab17b0664f42 Matthew Auld 2025-08-18 170 /*
0bab17b0664f42 Matthew Auld 2025-08-18 171 * Protect against concurrent instances of this function and
0bab17b0664f42 Matthew Auld 2025-08-18 172 * the critical exec sections
0bab17b0664f42 Matthew Auld 2025-08-18 173 */
0bab17b0664f42 Matthew Auld 2025-08-18 174 xe_vm_assert_held(vm);
0bab17b0664f42 Matthew Auld 2025-08-18 175
0bab17b0664f42 Matthew Auld 2025-08-18 176 if (!mmu_interval_read_retry(&uvma->userptr.notifier,
0bab17b0664f42 Matthew Auld 2025-08-18 @177 uvma->userptr.notifier_seq))
0bab17b0664f42 Matthew Auld 2025-08-18 178 uvma->userptr.notifier_seq -= 2;
0bab17b0664f42 Matthew Auld 2025-08-18 179 __vma_userptr_invalidate(vm, uvma);
0bab17b0664f42 Matthew Auld 2025-08-18 180 }
0bab17b0664f42 Matthew Auld 2025-08-18 181 #endif
0bab17b0664f42 Matthew Auld 2025-08-18 182
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-19 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 15:21 [PATCH v5 0/8] Replace xe_hmm with gpusvm Matthew Auld
2025-08-18 15:21 ` [PATCH v5 1/8] drm/gpusvm: fix hmm_pfn_to_map_order() usage Matthew Auld
2025-08-18 17:39 ` Matthew Brost
2025-09-02 9:10 ` Francois Dugast
2025-09-02 10:23 ` Matthew Auld
2025-08-18 15:21 ` [PATCH v5 2/8] drm/gpusvm: use more selective dma dir in get_pages() Matthew Auld
2025-08-18 15:21 ` [PATCH v5 3/8] drm/gpusvm: pull out drm_gpusvm_pages substructure Matthew Auld
2025-08-18 15:21 ` [PATCH v5 4/8] drm/gpusvm: refactor core API to use pages struct Matthew Auld
2025-08-18 15:21 ` [PATCH v5 5/8] drm/gpusvm: export drm_gpusvm_pages API Matthew Auld
2025-08-18 15:21 ` [PATCH v5 6/8] drm/xe/vm: split userptr bits into separate file Matthew Auld
2025-08-18 15:22 ` [PATCH v5 7/8] drm/xe/userptr: replace xe_hmm with gpusvm Matthew Auld
2025-08-19 0:18 ` kernel test robot [this message]
2025-08-18 15:22 ` [PATCH v5 8/8] drm/xe/pt: unify xe_pt_svm_pre_commit with userptr Matthew Auld
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=202508190722.CIuroUt0-lkp@intel.com \
--to=lkp@intel.com \
--cc=dafna.hirschfeld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=llvm@lists.linux.dev \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).