From: Jason Gunthorpe <jgg@nvidia.com>
To: kbuild-all@lists.01.org
Subject: Re: ERROR: modpost: "zap_vma_ptes" undefined!
Date: Sun, 28 Mar 2021 16:52:41 -0300 [thread overview]
Message-ID: <20210328195241.GW2356281@nvidia.com> (raw)
In-Reply-To: <202103241611.sznsZyvf-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
On Wed, Mar 24, 2021 at 08:59:13AM +0000, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 7acac4b3196caee5e21fb5ea53f8bc124e6a16fc
> commit: 179209fa12709a3df8888c323b37315da2683c24 vfio: IOMMU_API should be selected
> date: 8 days ago
> config: riscv-randconfig-r016-20210324 (attached as .config)
> compiler: riscv64-linux-gcc (GCC) 9.3.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/torvalds/linux.git/commit/?id=179209fa12709a3df8888c323b37315da2683c24
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 179209fa12709a3df8888c323b37315da2683c24
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
>
> 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 >>, old ones prefixed by <<):
>
> >> ERROR: modpost: "zap_vma_ptes" [drivers/vfio/pci/vfio-pci.ko] undefined!
This is the because of the patch ordering that Cornelia mentioned,
!MMU is fixed in the next patch
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
Eric Auger <eric.auger@redhat.com>
Subject: Re: ERROR: modpost: "zap_vma_ptes" undefined!
Date: Sun, 28 Mar 2021 16:52:41 -0300 [thread overview]
Message-ID: <20210328195241.GW2356281@nvidia.com> (raw)
In-Reply-To: <202103241611.sznsZyvf-lkp@intel.com>
On Wed, Mar 24, 2021 at 08:59:13AM +0000, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 7acac4b3196caee5e21fb5ea53f8bc124e6a16fc
> commit: 179209fa12709a3df8888c323b37315da2683c24 vfio: IOMMU_API should be selected
> date: 8 days ago
> config: riscv-randconfig-r016-20210324 (attached as .config)
> compiler: riscv64-linux-gcc (GCC) 9.3.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/torvalds/linux.git/commit/?id=179209fa12709a3df8888c323b37315da2683c24
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 179209fa12709a3df8888c323b37315da2683c24
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
>
> 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 >>, old ones prefixed by <<):
>
> >> ERROR: modpost: "zap_vma_ptes" [drivers/vfio/pci/vfio-pci.ko] undefined!
This is the because of the patch ordering that Cornelia mentioned,
!MMU is fixed in the next patch
Jason
next prev parent reply other threads:[~2021-03-28 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 8:59 ERROR: modpost: "zap_vma_ptes" undefined! kernel test robot
2021-03-24 8:59 ` kernel test robot
2021-03-28 19:52 ` Jason Gunthorpe [this message]
2021-03-28 19:52 ` Jason Gunthorpe
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=20210328195241.GW2356281@nvidia.com \
--to=jgg@nvidia.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.