dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: 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>,
	"Matthew Brost" <matthew.brost@intel.com>
Subject: Re: [PATCH v3 6/7] drm/xe/userptr: replace xe_hmm with gpusvm
Date: Thu, 24 Apr 2025 22:42:11 +0800	[thread overview]
Message-ID: <202504242203.MfhcD5LA-lkp@intel.com> (raw)
In-Reply-To: <20250424121827.862729-15-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-20250424]
[cannot apply to drm-exynos/exynos-drm-next linus/master drm/drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip v6.15-rc3]
[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/20250424-202128
base:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:    https://lore.kernel.org/r/20250424121827.862729-15-matthew.auld%40intel.com
patch subject: [PATCH v3 6/7] drm/xe/userptr: replace xe_hmm with gpusvm
config: loongarch-randconfig-002-20250424 (https://download.01.org/0day-ci/archive/20250424/202504242203.MfhcD5LA-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250424/202504242203.MfhcD5LA-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/202504242203.MfhcD5LA-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/irqflags.h:19,
                    from include/linux/spinlock.h:59,
                    from include/linux/sched.h:2213,
                    from include/linux/ratelimit.h:6,
                    from include/linux/dev_printk.h:16,
                    from include/linux/device.h:15,
                    from include/drm/drm_print.h:31,
                    from drivers/gpu/drm/xe/xe_assert.h:11,
                    from drivers/gpu/drm/xe/xe_vm.h:9,
                    from drivers/gpu/drm/xe/xe_vm.c:6:
   arch/loongarch/include/asm/percpu.h:20:4: error: #error compiler support for the model attribute is necessary when a recent assembler is used
      20 | #  error compiler support for the model attribute is necessary when a recent assembler is used
         |    ^~~~~
   drivers/gpu/drm/xe/xe_vm.c: In function 'xe_vma_userptr_force_invalidate':
>> drivers/gpu/drm/xe/xe_vm.c:699:52: error: 'struct xe_userptr' has no member named 'notifier_seq'; did you mean 'notifier'?
     699 |                                      uvma->userptr.notifier_seq))
         |                                                    ^~~~~~~~~~~~
         |                                                    notifier
   drivers/gpu/drm/xe/xe_vm.c:700:31: error: 'struct xe_userptr' has no member named 'notifier_seq'; did you mean 'notifier'?
     700 |                 uvma->userptr.notifier_seq -= 2;
         |                               ^~~~~~~~~~~~
         |                               notifier

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for DRM_GPUSVM
   Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && DEVICE_PRIVATE [=n]
   Selected by [m]:
   - DRM_XE [=m] && HAS_IOMEM [=y] && DRM [=y] && PCI [=y] && MMU [=y] && (m [=m] && MODULES [=y] || KUNIT [=n]=y [=y])


vim +699 drivers/gpu/drm/xe/xe_vm.c

dd08ebf6c3525a Matthew Brost    2023-03-30  676  
100a5b8dadfca5 Thomas Hellström 2025-02-28  677  #if IS_ENABLED(CONFIG_DRM_XE_USERPTR_INVAL_INJECT)
100a5b8dadfca5 Thomas Hellström 2025-02-28  678  /**
100a5b8dadfca5 Thomas Hellström 2025-02-28  679   * xe_vma_userptr_force_invalidate() - force invalidate a userptr
100a5b8dadfca5 Thomas Hellström 2025-02-28  680   * @uvma: The userptr vma to invalidate
100a5b8dadfca5 Thomas Hellström 2025-02-28  681   *
100a5b8dadfca5 Thomas Hellström 2025-02-28  682   * Perform a forced userptr invalidation for testing purposes.
100a5b8dadfca5 Thomas Hellström 2025-02-28  683   */
100a5b8dadfca5 Thomas Hellström 2025-02-28  684  void xe_vma_userptr_force_invalidate(struct xe_userptr_vma *uvma)
100a5b8dadfca5 Thomas Hellström 2025-02-28  685  {
100a5b8dadfca5 Thomas Hellström 2025-02-28  686  	struct xe_vm *vm = xe_vma_vm(&uvma->vma);
100a5b8dadfca5 Thomas Hellström 2025-02-28  687  
100a5b8dadfca5 Thomas Hellström 2025-02-28  688  	/* Protect against concurrent userptr pinning */
100a5b8dadfca5 Thomas Hellström 2025-02-28  689  	lockdep_assert_held(&vm->lock);
100a5b8dadfca5 Thomas Hellström 2025-02-28  690  	/* Protect against concurrent notifiers */
a2cfe1a4a9e967 Matthew Auld     2025-04-24  691  	lockdep_assert_held(&vm->svm.gpusvm.notifier_lock);
100a5b8dadfca5 Thomas Hellström 2025-02-28  692  	/*
100a5b8dadfca5 Thomas Hellström 2025-02-28  693  	 * Protect against concurrent instances of this function and
100a5b8dadfca5 Thomas Hellström 2025-02-28  694  	 * the critical exec sections
100a5b8dadfca5 Thomas Hellström 2025-02-28  695  	 */
100a5b8dadfca5 Thomas Hellström 2025-02-28  696  	xe_vm_assert_held(vm);
100a5b8dadfca5 Thomas Hellström 2025-02-28  697  
100a5b8dadfca5 Thomas Hellström 2025-02-28  698  	if (!mmu_interval_read_retry(&uvma->userptr.notifier,
100a5b8dadfca5 Thomas Hellström 2025-02-28 @699  				     uvma->userptr.notifier_seq))
100a5b8dadfca5 Thomas Hellström 2025-02-28  700  		uvma->userptr.notifier_seq -= 2;
100a5b8dadfca5 Thomas Hellström 2025-02-28  701  	__vma_userptr_invalidate(vm, uvma);
100a5b8dadfca5 Thomas Hellström 2025-02-28  702  }
100a5b8dadfca5 Thomas Hellström 2025-02-28  703  #endif
100a5b8dadfca5 Thomas Hellström 2025-02-28  704  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-04-24 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 12:18 [PATCH v3 0/7] Replace xe_hmm with gpusvm Matthew Auld
2025-04-24 12:18 ` [PATCH v3 1/7] drm/gpusvm: fix hmm_pfn_to_map_order() usage Matthew Auld
2025-04-24 12:18 ` [PATCH v3 2/7] drm/gpusvm: use more selective dma dir in get_pages() Matthew Auld
2025-04-24 12:18 ` [PATCH v3 3/7] drm/gpusvm: pull out drm_gpusvm_pages substructure Matthew Auld
2025-04-24 12:18 ` [PATCH v3 4/7] drm/gpusvm: refactor core API to use pages struct Matthew Auld
2025-04-24 21:47   ` Matthew Brost
2025-04-24 12:18 ` [PATCH v3 5/7] drm/gpusvm: export drm_gpusvm_pages API Matthew Auld
2025-04-24 22:01   ` Matthew Brost
2025-04-24 22:04     ` Matthew Brost
2025-04-24 12:18 ` [PATCH v3 6/7] drm/xe/userptr: replace xe_hmm with gpusvm Matthew Auld
2025-04-24 14:21   ` kernel test robot
2025-04-24 14:42   ` kernel test robot [this message]
2025-04-24 23:17   ` Matthew Brost
2025-04-25 14:00   ` kernel test robot
2025-04-28  3:47   ` Dafna Hirschfeld
2025-04-24 12:18 ` [PATCH v3 7/7] drm/xe/pt: unify xe_pt_svm_pre_commit with userptr Matthew Auld
2025-04-24 15:43   ` kernel test robot
2025-04-24 23:18   ` Matthew Brost

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=202504242203.MfhcD5LA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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