mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: ankita@nvidia.com, jgg@ziepe.ca, yishaih@nvidia.com,
	skolothumtho@nvidia.com, kevin.tian@intel.com, alex@shazbot.org,
	aniketa@nvidia.com, vsethi@nvidia.com, mochs@nvidia.com
Cc: oe-kbuild-all@lists.linux.dev, Yunxiang.Li@amd.com,
	yi.l.liu@intel.com, zhangdongdong@eswincomputing.com,
	avihaih@nvidia.com, bhelgaas@google.com, peterx@redhat.com,
	pstanner@redhat.com, apopple@nvidia.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, cjia@nvidia.com,
	kwankhede@nvidia.com, targupta@nvidia.com, zhiw@nvidia.com,
	danw@nvidia.com, dnigam@nvidia.com, kjaju@nvidia.com
Subject: Re: [PATCH v1 3/6] vfio/nvgrace-gpu: Add support for huge pfnmap
Date: Tue, 18 Nov 2025 14:12:16 +0800	[thread overview]
Message-ID: <202511181317.hOMn5k0o-lkp@intel.com> (raw)
In-Reply-To: <20251117124159.3560-4-ankita@nvidia.com>

Hi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on awilliam-vfio/next]
[also build test WARNING on awilliam-vfio/for-linus linus/master v6.18-rc6 next-20251118]
[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/ankita-nvidia-com/vfio-nvgrace-gpu-Use-faults-to-map-device-memory/20251117-205950
base:   https://github.com/awilliam/linux-vfio.git next
patch link:    https://lore.kernel.org/r/20251117124159.3560-4-ankita%40nvidia.com
patch subject: [PATCH v1 3/6] vfio/nvgrace-gpu: Add support for huge pfnmap
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20251118/202511181317.hOMn5k0o-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251118/202511181317.hOMn5k0o-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/202511181317.hOMn5k0o-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/vfio/pci/nvgrace-gpu/main.c: In function 'nvgrace_gpu_aligned_devmem_size':
>> drivers/vfio/pci/nvgrace-gpu/main.c:179:7: warning: 'CONFIG_ARCH_SUPPORTS_PUD_PFNMAP' is not defined, evaluates to '0' [-Wundef]
     179 | #elif CONFIG_ARCH_SUPPORTS_PUD_PFNMAP
         |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


vim +179 drivers/vfio/pci/nvgrace-gpu/main.c

   174	
   175	static size_t nvgrace_gpu_aligned_devmem_size(size_t memlength)
   176	{
   177	#ifdef CONFIG_ARCH_SUPPORTS_PMD_PFNMAP
   178		return ALIGN(memlength, PMD_SIZE);
 > 179	#elif CONFIG_ARCH_SUPPORTS_PUD_PFNMAP
   180		return ALIGN(memlength, PUD_SIZE);
   181	#endif
   182		return memlength;
   183	}
   184	

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

  reply	other threads:[~2025-11-18  6:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 12:41 [PATCH v1 0/6] vfio/nvgrace-gpu: Support huge PFNMAP and wait ankita
2025-11-17 12:41 ` [PATCH v1 1/6] vfio/nvgrace-gpu: Use faults to map device memory ankita
2025-11-17 12:41 ` [PATCH v1 2/6] vfio: export function to map the VMA ankita
2025-11-17 12:41 ` [PATCH v1 3/6] vfio/nvgrace-gpu: Add support for huge pfnmap ankita
2025-11-18  6:12   ` kernel test robot [this message]
2025-11-17 12:41 ` [PATCH v1 4/6] vfio: export vfio_find_cap_start ankita
2025-11-17 12:41 ` [PATCH v1 5/6] vfio/nvgrace-gpu: split the code to wait for GPU ready ankita
2025-11-17 12:41 ` [PATCH v1 6/6] vfio/nvgrace-gpu: vfio/nvgrace-gpu: wait for the GPU mem to be ready ankita
2025-11-18  0:45   ` Alex Williamson

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=202511181317.hOMn5k0o-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Yunxiang.Li@amd.com \
    --cc=alex@shazbot.org \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=apopple@nvidia.com \
    --cc=avihaih@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=cjia@nvidia.com \
    --cc=danw@nvidia.com \
    --cc=dnigam@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kjaju@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochs@nvidia.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterx@redhat.com \
    --cc=pstanner@redhat.com \
    --cc=skolothumtho@nvidia.com \
    --cc=targupta@nvidia.com \
    --cc=vsethi@nvidia.com \
    --cc=yi.l.liu@intel.com \
    --cc=yishaih@nvidia.com \
    --cc=zhangdongdong@eswincomputing.com \
    --cc=zhiw@nvidia.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

all inboxes | Powered by JetHome®