From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>
Subject: drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgm200.c:32:9: sparse: sparse: cast truncates bits from constant value (100000000 becomes 0)
Date: Sun, 14 Dec 2025 07:34:54 +0800 [thread overview]
Message-ID: <202512140713.HUSp33rF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4a298a43f5e339f48d2dda0665c02b88ee9a4e03
commit: b8c9c3b822fe8e033b9802516f6466099d915488 um: stop using PCI port I/O
date: 7 months ago
config: um-randconfig-r121-20251213 (https://download.01.org/0day-ci/archive/20251214/202512140713.HUSp33rF-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251214/202512140713.HUSp33rF-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/202512140713.HUSp33rF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgm200.c:32:9: sparse: sparse: cast truncates bits from constant value (100000000 becomes 0)
drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgm200.c:57:9: sparse: sparse: cast truncates bits from constant value (800000000 becomes 0)
vim +32 drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgm200.c
5f300fed645597 Ben Skeggs 2017-11-01 26
e12cf6ad43888c Ben Skeggs 2017-11-01 27 static void
e12cf6ad43888c Ben Skeggs 2017-11-01 28 gm200_vmm_pgt_sparse(struct nvkm_vmm *vmm,
e12cf6ad43888c Ben Skeggs 2017-11-01 29 struct nvkm_mmu_pt *pt, u32 ptei, u32 ptes)
e12cf6ad43888c Ben Skeggs 2017-11-01 30 {
e12cf6ad43888c Ben Skeggs 2017-11-01 31 /* VALID_FALSE + VOL tells the MMU to treat the PTE as sparse. */
e12cf6ad43888c Ben Skeggs 2017-11-01 @32 VMM_FO064(pt, vmm, ptei * 8, BIT_ULL(32) /* VOL. */, ptes);
e12cf6ad43888c Ben Skeggs 2017-11-01 33 }
e12cf6ad43888c Ben Skeggs 2017-11-01 34
:::::: The code at line 32 was first introduced by commit
:::::: e12cf6ad43888c152c3b2edb59525587cd98a227 drm/nouveau/mmu/gm200,gm20b: implement new vmm backend
:::::: TO: Ben Skeggs <bskeggs@redhat.com>
:::::: CC: Ben Skeggs <bskeggs@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-13 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 23:34 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-13 0:40 kernel test robot
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=202512140713.HUSp33rF-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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®