From: kernel test robot <lkp@intel.com>
To: Eli Cohen <elic@nvidia.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [linux-next:master 9362/10638] mlx5_vnet.c:undefined reference to `.vringh_getdesc_iotlb'
Date: Fri, 27 Aug 2021 04:48:27 +0800 [thread overview]
Message-ID: <202108270420.Ie0qPLvy-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2830 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 88fac11862d38306dd0d2398015744877140390d
commit: 4d39eaf343432091a93d01c86fde2b4e168df642 [9362/10638] vdpa/mlx5: Add multiqueue support
config: powerpc-buildonly-randconfig-r006-20210825 (attached as .config)
compiler: powerpc64-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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4d39eaf343432091a93d01c86fde2b4e168df642
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 4d39eaf343432091a93d01c86fde2b4e168df642
# 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=powerpc 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 >>):
powerpc64-linux-ld: warning: discarding dynamic section .glink
powerpc64-linux-ld: warning: discarding dynamic section .plt
powerpc64-linux-ld: linkage table error against `vringh_set_iotlb'
powerpc64-linux-ld: stubs don't match calculated size
powerpc64-linux-ld: can not build stubs: bad value
powerpc64-linux-ld: drivers/vdpa/mlx5/net/mlx5_vnet.o: in function `.setup_driver':
mlx5_vnet.c:(.text+0x5064): undefined reference to `.vringh_init_iotlb'
powerpc64-linux-ld: drivers/vdpa/mlx5/net/mlx5_vnet.o: in function `.mlx5_cvq_kick_handler':
>> mlx5_vnet.c:(.text+0x59bc): undefined reference to `.vringh_getdesc_iotlb'
powerpc64-linux-ld: mlx5_vnet.c:(.text+0x59e4): undefined reference to `.vringh_iov_pull_iotlb'
powerpc64-linux-ld: mlx5_vnet.c:(.text+0x5a50): undefined reference to `.vringh_iov_push_iotlb'
powerpc64-linux-ld: mlx5_vnet.c:(.text+0x5a68): undefined reference to `.vringh_complete_iotlb'
powerpc64-linux-ld: mlx5_vnet.c:(.text+0x5abc): undefined reference to `.vringh_need_notify_iotlb'
powerpc64-linux-ld: mlx5_vnet.c:(.text+0x5b1c): undefined reference to `.vringh_getdesc_iotlb'
powerpc64-linux-ld: mlx5_vnet.c:(.text+0x5b98): undefined reference to `.vringh_iov_pull_iotlb'
powerpc64-linux-ld: mlx5_vnet.c:(.text+0x5c6c): undefined reference to `.vringh_iov_pull_iotlb'
powerpc64-linux-ld: drivers/vdpa/mlx5/core/resources.o: in function `.mlx5_vdpa_alloc_resources':
resources.c:(.text+0xb74): undefined reference to `.vringh_set_iotlb'
---
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: 37677 bytes --]
reply other threads:[~2021-08-26 20:49 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=202108270420.Ie0qPLvy-lkp@intel.com \
--to=lkp@intel.com \
--cc=elic@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.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