From: kernel test robot <lkp@intel.com>
To: Mohamed Ahmed <mohamedahmedegypt2001@gmail.com>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
Mary Guillemard <mary@mary.zone>,
Faith Ekstrand <faith.ekstrand@collabora.com>,
Lyude Paul <lyude@redhat.com>, Danilo Krummrich <dakr@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
nouveau@lists.freedesktop.org,
Mohamed Ahmed <mohamedahmedegypt2001@gmail.com>,
James Jones <jajones@nvidia.com>
Subject: Re: [PATCH v5 2/5] drm/nouveau/uvmm: Allow larger pages
Date: Mon, 10 Nov 2025 21:37:18 +0800 [thread overview]
Message-ID: <202511102116.qWX79pIo-lkp@intel.com> (raw)
In-Reply-To: <20251108194919.68754-3-mohamedahmedegypt2001@gmail.com>
Hi Mohamed,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.18-rc5 next-20251110]
[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/Mohamed-Ahmed/drm-nouveau-uvmm-Prepare-for-larger-pages/20251109-035142
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20251108194919.68754-3-mohamedahmedegypt2001%40gmail.com
patch subject: [PATCH v5 2/5] drm/nouveau/uvmm: Allow larger pages
config: i386-randconfig-141-20251110 (https://download.01.org/0day-ci/archive/20251110/202511102116.qWX79pIo-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251110/202511102116.qWX79pIo-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/202511102116.qWX79pIo-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/nouveau/nouveau_uvmm.c:508:16: error: incompatible pointer types passing 'struct drm_device *' to parameter of type 'const struct device *' [-Werror,-Wincompatible-pointer-types]
508 | dev_warn_once(op->gem.obj->dev, "Could not find an appropriate page size.\n");
| ^~~~~~~~~~~~~~~~
include/linux/dev_printk.h:201:27: note: expanded from macro 'dev_warn_once'
201 | dev_level_once(dev_warn, dev, fmt, ##__VA_ARGS__)
| ^~~
include/linux/dev_printk.h:181:13: note: expanded from macro 'dev_level_once'
181 | dev_level(dev, fmt, ##__VA_ARGS__); \
| ^~~
include/linux/dev_printk.h:156:49: note: expanded from macro 'dev_warn'
156 | dev_printk_index_wrap(_dev_warn, KERN_WARNING, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~
include/linux/dev_printk.h:110:11: note: expanded from macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~
include/linux/dev_printk.h:52:37: note: passing argument to parameter 'dev' here
52 | void _dev_warn(const struct device *dev, const char *fmt, ...);
| ^
1 error generated.
vim +508 drivers/gpu/drm/nouveau/nouveau_uvmm.c
466
467 static u8
468 select_page_shift(struct nouveau_uvmm *uvmm, struct drm_gpuva_op_map *op)
469 {
470 struct nouveau_bo *nvbo = nouveau_gem_object(op->gem.obj);
471
472 /* nouveau_bo_fixup_align() guarantees that the page size will be aligned
473 * for most cases, but it can't handle cases where userspace allocates with
474 * a size and then binds with a smaller granularity. So in order to avoid
475 * breaking old userspace, we need to ensure that the VA is actually
476 * aligned before using it, and if it isn't, then we downgrade to the first
477 * granularity that will fit, which is optimal from a correctness and
478 * performance perspective.
479 */
480 if (op_map_aligned_to_page_shift(op, nvbo->page))
481 return nvbo->page;
482
483 struct nouveau_mem *mem = nouveau_mem(nvbo->bo.resource);
484 struct nvif_vmm *vmm = &uvmm->vmm.vmm;
485 int i;
486
487 /* If the given granularity doesn't fit, let's find one that will fit. */
488 for (i = 0; i < vmm->page_nr; i++) {
489 /* Ignore anything that is bigger or identical to the BO preference. */
490 if (vmm->page[i].shift >= nvbo->page)
491 continue;
492
493 /* Skip incompatible domains. */
494 if ((mem->mem.type & NVIF_MEM_VRAM) && !vmm->page[i].vram)
495 continue;
496 if ((mem->mem.type & NVIF_MEM_HOST) &&
497 (!vmm->page[i].host || vmm->page[i].shift > PAGE_SHIFT))
498 continue;
499
500 /* If it fits, return the proposed shift. */
501 if (op_map_aligned_to_page_shift(op, vmm->page[i].shift))
502 return vmm->page[i].shift;
503 }
504
505 /* If we get here then nothing can reconcile the requirements. This should never
506 * happen.
507 */
> 508 dev_warn_once(op->gem.obj->dev, "Could not find an appropriate page size.\n");
509
510 return PAGE_SHIFT;
511 }
512
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-10 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 19:49 [PATCH v5 0/5] drm/nouveau: Enable variable page sizes and compression Mohamed Ahmed
2025-11-08 19:49 ` [PATCH v5 1/5] drm/nouveau/uvmm: Prepare for larger pages Mohamed Ahmed
2025-11-08 19:49 ` [PATCH v5 2/5] drm/nouveau/uvmm: Allow " Mohamed Ahmed
2025-11-10 10:06 ` kernel test robot
2025-11-10 13:37 ` kernel test robot [this message]
2025-11-08 19:49 ` [PATCH v5 3/5] drm/nouveau/mmu/gp100: Remove unused/broken support for compression Mohamed Ahmed
2025-11-08 19:49 ` [PATCH v5 4/5] drm/nouveau/mmu/tu102: Add support for compressed kinds Mohamed Ahmed
2025-11-08 19:49 ` [PATCH v5 5/5] drm/nouveau/drm: Bump the driver version to 1.4.1 to report new features Mohamed Ahmed
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=202511102116.qWX79pIo-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith.ekstrand@collabora.com \
--cc=jajones@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mary@mary.zone \
--cc=mohamedahmedegypt2001@gmail.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®