From: kernel test robot <lkp@intel.com>
To: Liu Yi L <yi.l.liu@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [luxis1999-dev-iommu:iommufd-vfio-v5.16-rc1 29/32] iommufd.c:undefined reference to `vfio_iommu_type1_map_dma'
Date: Fri, 5 Nov 2021 06:28:49 +0800 [thread overview]
Message-ID: <202111050642.1mtdVEMW-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3852 bytes --]
tree: https://github.com/luxis1999/dev-iommu iommufd-vfio-v5.16-rc1
head: 0c6c7bdb5b3f7d4c8e6b03d34a59ac6bf3d02539
commit: 465aafaf97510d09bd68700c80ed3bb87db45077 [29/32] iommufd: Add IOMMU_IOAS_[UN]MAP_DMA
config: openrisc-randconfig-r002-20211105 (attached as .config)
compiler: or1k-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/luxis1999/dev-iommu/commit/465aafaf97510d09bd68700c80ed3bb87db45077
git remote add luxis1999-dev-iommu https://github.com/luxis1999/dev-iommu
git fetch --no-tags luxis1999-dev-iommu iommufd-vfio-v5.16-rc1
git checkout 465aafaf97510d09bd68700c80ed3bb87db45077
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=openrisc SHELL=/bin/bash
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 >>):
or1k-linux-ld: drivers/iommufd/iommufd.o: in function `ioas_put':
iommufd.c:(.text+0x88): undefined reference to `vfio_iommu_type1_release'
iommufd.c:(.text+0x88): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_type1_release'
or1k-linux-ld: drivers/iommufd/iommufd.o: in function `iommufd_process_dma_op':
>> iommufd.c:(.text+0x490): undefined reference to `vfio_iommu_type1_map_dma'
iommufd.c:(.text+0x490): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_type1_map_dma'
>> or1k-linux-ld: iommufd.c:(.text+0x4cc): undefined reference to `vfio_iommu_type1_unmap_dma'
iommufd.c:(.text+0x4cc): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_type1_unmap_dma'
or1k-linux-ld: drivers/iommufd/iommufd.o: in function `iommufd_ioas_alloc':
iommufd.c:(.text+0x6a4): undefined reference to `vfio_iommu_type1_open'
iommufd.c:(.text+0x6a4): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_type1_open'
>> or1k-linux-ld: iommufd.c:(.text+0x788): undefined reference to `vfio_iommu_type1_release'
iommufd.c:(.text+0x788): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_type1_release'
or1k-linux-ld: iommufd.c:(.text+0x7a0): undefined reference to `vfio_iommu_type1_release'
iommufd.c:(.text+0x7a0): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_type1_release'
or1k-linux-ld: drivers/iommufd/iommufd.o: in function `iommufd_get_device_info':
iommufd.c:(.text+0x98c): undefined reference to `vfio_device_add_iova_cap'
iommufd.c:(.text+0x98c): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_device_add_iova_cap'
or1k-linux-ld: drivers/iommufd/iommufd.o: in function `iommufd_device_attach_ioas':
iommufd.c:(.text+0xec0): undefined reference to `vfio_iommu_add_group'
iommufd.c:(.text+0xec0): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_add_group'
>> or1k-linux-ld: iommufd.c:(.text+0xfcc): undefined reference to `vfio_iommu_remove_group'
iommufd.c:(.text+0xfcc): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_remove_group'
or1k-linux-ld: drivers/iommufd/iommufd.o: in function `iommufd_device_detach_ioas':
iommufd.c:(.text+0x1074): undefined reference to `vfio_iommu_remove_group'
iommufd.c:(.text+0x1074): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `vfio_iommu_remove_group'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25419 bytes --]
reply other threads:[~2021-11-04 22:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202111050642.1mtdVEMW-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.l.liu@intel.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