From: kernel test robot <lkp@intel.com>
To: Ankit Agrawal <ankita@nvidia.com>, alex@shazbot.org, kvm@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
jgg@ziepe.ca, yishaih@nvidia.com, skolothumtho@nvidia.com,
kevin.tian@intel.com, ankita@nvidia.com, bhelgaas@google.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 1/1] vfio/nvgrace-gpu: Add Blackwell-Next GPU readiness check via CXL DVSEC
Date: Tue, 21 Apr 2026 04:09:41 +0800 [thread overview]
Message-ID: <202604210425.SVQZamM3-lkp@intel.com> (raw)
In-Reply-To: <20260416014504.63067-1-ankita@nvidia.com>
Hi Ankit,
kernel test robot noticed the following build errors:
[auto build test ERROR on awilliam-vfio/next]
[also build test ERROR on awilliam-vfio/for-linus pci/next pci/for-linus linus/master v7.0 next-20260420]
[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/Ankit-Agrawal/vfio-nvgrace-gpu-Add-Blackwell-Next-GPU-readiness-check-via-CXL-DVSEC/20260419-053131
base: https://github.com/awilliam/linux-vfio.git next
patch link: https://lore.kernel.org/r/20260416014504.63067-1-ankita%40nvidia.com
patch subject: [PATCH v3 1/1] vfio/nvgrace-gpu: Add Blackwell-Next GPU readiness check via CXL DVSEC
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20260421/202604210425.SVQZamM3-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260421/202604210425.SVQZamM3-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/202604210425.SVQZamM3-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/vfio/pci/nvgrace-gpu/main.c:296:23: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
296 | mem_active_timeout = FIELD_GET(PCI_DVSEC_CXL_MEM_ACTIVE_TIMEOUT,
| ^
1 error generated.
vim +/FIELD_GET +296 drivers/vfio/pci/nvgrace-gpu/main.c
280
281 static int nvgrace_gpu_wait_device_ready_cxl(struct nvgrace_gpu_pci_core_device *nvdev)
282 {
283 struct pci_dev *pdev = nvdev->core_device.pdev;
284 int cxl_dvsec = nvdev->cxl_dvsec;
285 unsigned long mem_info_valid_deadline;
286 unsigned long timeout;
287 u32 dvsec_memory_status;
288 u8 mem_active_timeout;
289
290 pci_read_config_dword(pdev, cxl_dvsec + PCI_DVSEC_CXL_RANGE_SIZE_LOW(0),
291 &dvsec_memory_status);
292
293 if (cxl_dvsec_mem_is_active(dvsec_memory_status))
294 return 0;
295
> 296 mem_active_timeout = FIELD_GET(PCI_DVSEC_CXL_MEM_ACTIVE_TIMEOUT,
297 dvsec_memory_status);
298
299 timeout = jiffies +
300 msecs_to_jiffies(cxl_mem_active_timeout_ms(mem_active_timeout));
301
302 mem_info_valid_deadline = jiffies + msecs_to_jiffies(POLL_QUANTUM_MS);
303
304 do {
305 pci_read_config_dword(pdev,
306 cxl_dvsec + PCI_DVSEC_CXL_RANGE_SIZE_LOW(0),
307 &dvsec_memory_status);
308
309 if (cxl_dvsec_mem_is_active(dvsec_memory_status))
310 return 0;
311
312 /* Bail early if MEM_INFO_VALID is not set within 1 second */
313 if (!(dvsec_memory_status & PCI_DVSEC_CXL_MEM_INFO_VALID) &&
314 time_after(jiffies, mem_info_valid_deadline))
315 return -ETIME;
316
317 msleep(POLL_QUANTUM_MS);
318 } while (!time_after(jiffies, timeout));
319
320 return -ETIME;
321 }
322
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-04-20 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 1:45 [PATCH v3 1/1] vfio/nvgrace-gpu: Add Blackwell-Next GPU readiness check via CXL DVSEC Ankit Agrawal
2026-04-17 7:16 ` Tian, Kevin
2026-04-20 13:20 ` Nirmoy Das
2026-04-20 20:09 ` kernel test robot [this message]
2026-04-21 2:37 ` 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=202604210425.SVQZamM3-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@shazbot.org \
--cc=ankita@nvidia.com \
--cc=bhelgaas@google.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skolothumtho@nvidia.com \
--cc=yishaih@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