From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v1 3/4] vfio: Try to enable IOPF for VFIO devices
Date: Wed, 27 Jan 2021 14:31:11 +0800 [thread overview]
Message-ID: <202101271405.aIDgED0R-lkp@intel.com> (raw)
In-Reply-To: <20210125090402.1429-4-lushenming@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2446 bytes --]
Hi Shenming,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on vfio/next]
[also build test ERROR on v5.11-rc5 next-20210125]
[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]
url: https://github.com/0day-ci/linux/commits/Shenming-Lu/vfio-type1-Add-a-bitmap-to-track-IOPF-mapped-pages/20210126-141137
base: https://github.com/awilliam/linux-vfio.git next
config: x86_64-rhel-8.3 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/275e8cc280f586d526fb8bf83f6b1575e52256a1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Shenming-Lu/vfio-type1-Add-a-bitmap-to-track-IOPF-mapped-pages/20210126-141137
git checkout 275e8cc280f586d526fb8bf83f6b1575e52256a1
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/vfio/vfio.c: In function 'vfio_device_enable_iopf':
>> drivers/vfio/vfio.c:541:34: error: 'IOMMU_DEV_FEAT_IOPF' undeclared (first use in this function); did you mean 'IOMMU_DEV_FEAT_SVA'?
541 | if (!iommu_dev_has_feature(dev, IOMMU_DEV_FEAT_IOPF))
| ^~~~~~~~~~~~~~~~~~~
| IOMMU_DEV_FEAT_SVA
drivers/vfio/vfio.c:541:34: note: each undeclared identifier is reported only once for each function it appears in
vim +541 drivers/vfio/vfio.c
532
533 /**
534 * Device objects - create, release, get, put, search
535 */
536
537 static void vfio_device_enable_iopf(struct vfio_device *device)
538 {
539 struct device *dev = device->dev;
540
> 541 if (!iommu_dev_has_feature(dev, IOMMU_DEV_FEAT_IOPF))
542 return;
543
544 if (WARN_ON(iommu_register_device_fault_handler(dev,
545 vfio_iommu_dev_fault_handler, dev)))
546 return;
547
548 device->iopf_enabled = true;
549 }
550
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 40834 bytes --]
next prev parent reply other threads:[~2021-01-27 6:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 9:03 [RFC PATCH v1 0/4] vfio: Add IOPF support for VFIO passthrough Shenming Lu
2021-01-25 9:03 ` [RFC PATCH v1 1/4] vfio/type1: Add a bitmap to track IOPF mapped pages Shenming Lu
2021-01-29 22:58 ` Alex Williamson
2021-01-30 9:31 ` Shenming Lu
2021-01-25 9:04 ` [RFC PATCH v1 2/4] vfio: Add a page fault handler Shenming Lu
2021-01-27 17:42 ` Christoph Hellwig
2021-01-28 6:10 ` Shenming Lu
2021-01-25 9:04 ` [RFC PATCH v1 3/4] vfio: Try to enable IOPF for VFIO devices Shenming Lu
2021-01-26 14:33 ` kernel test robot
2021-01-27 6:31 ` kernel test robot [this message]
2021-01-29 22:42 ` Alex Williamson
2021-01-30 9:31 ` Shenming Lu
2021-01-25 9:04 ` [RFC PATCH v1 4/4] vfio: Allow to pin and map dynamically Shenming Lu
2021-01-29 22:57 ` [RFC PATCH v1 0/4] vfio: Add IOPF support for VFIO passthrough Alex Williamson
2021-01-30 9:30 ` Shenming Lu
2021-02-01 7:56 ` Tian, Kevin
2021-02-02 6:41 ` Shenming Lu
2021-02-04 6:52 ` Tian, Kevin
2021-02-05 10:37 ` Jean-Philippe Brucker
2021-02-07 8:20 ` Tian, Kevin
2021-02-07 11:47 ` Shenming Lu
2021-02-09 11:06 ` Liu, Yi L
2021-02-10 8:02 ` Shenming Lu
2021-03-18 7:53 ` Shenming Lu
2021-03-18 9:07 ` Tian, Kevin
2021-03-18 11:53 ` Shenming Lu
2021-03-18 12:32 ` Tian, Kevin
2021-03-18 12:47 ` Shenming Lu
2021-03-19 0:33 ` Lu Baolu
2021-03-19 1:30 ` Keqian Zhu
2021-03-20 1:35 ` Lu Baolu
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=202101271405.aIDgED0R-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.