From: kernel test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: "Paul Gazzillo" <paul@pgazz.com>,
"Necip Fazil Yildiran" <fazilyildiran@gmail.com>,
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: Fri, 25 Apr 2025 22:00:33 +0800 [thread overview]
Message-ID: <202504252124.jQDkibSg-lkp@intel.com> (raw)
In-Reply-To: <20250424121827.862729-15-matthew.auld@intel.com>
Hi Matthew,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING 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: alpha-kismet-CONFIG_DRM_GPUSVM-CONFIG_DRM_XE-0-0 (https://download.01.org/0day-ci/archive/20250425/202504252124.jQDkibSg-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20250425/202504252124.jQDkibSg-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/202504252124.jQDkibSg-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for DRM_GPUSVM when selected by DRM_XE
WARNING: unmet direct dependencies detected for LEDS_EXPRESSWIRE
Depends on [n]: GPIOLIB [=n] || NEW_LEDS [=y] && GPIOLIB [=n]
Selected by [y]:
- BACKLIGHT_KTD2801 [=y] && HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y]
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])
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-25 14:01 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
2025-04-24 23:17 ` Matthew Brost
2025-04-25 14:00 ` kernel test robot [this message]
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=202504252124.jQDkibSg-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fazilyildiran@gmail.com \
--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=paul@pgazz.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