netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [vhost:linux-next 8/13] include/linux/vringh.h:18:10: fatal error: linux/vhost_iotlb.h: No such file or directory
Date: Mon, 30 Mar 2020 10:46:35 +0800	[thread overview]
Message-ID: <f1270de5-7a2c-76d2-431c-34364def851a@redhat.com> (raw)
In-Reply-To: <202003292026.dP7OOeCi%lkp@intel.com>


On 2020/3/29 下午8:08, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> head:   f44a63f9ebf66a450c101084a35a3ef158ead209
> commit: c43908b0b9a900bd51f861f4c57b83cfd932f4d2 [8/13] vringh: IOTLB support
> config: arm-em_x270_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> reproduce:
>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>          chmod +x ~/bin/make.cross
>          git checkout c43908b0b9a900bd51f861f4c57b83cfd932f4d2


I could not find this commit in the above branch.


>          # save the attached .config to linux build tree
>          GCC_VERSION=9.3.0 make.cross ARCH=arm


Try to use commit dc3b0673ae5efb73edab66ec5c2f074272e9a4df.

But this command does not work (I remember it used to work):

# GCC_VERSION=9.3.0 make.cross ARCH=arm
cd: received redirection to 
`https://download.01.org/0day-ci/cross-package/'
lftpget -c 
https://download.01.org/0day-ci/cross-package/./gcc-9.3.0-nolibc/x86_64-gcc-9.3.0-nolibc_arm-linux-gnueabihf.tar.xz
tar Jxf 
gcc-9.3.0-nolibc/x86_64-gcc-9.3.0-nolibc_arm-linux-gnueabihf.tar.xz -C 
/root/0day
No cross compiler for arm
setup_crosstool failed


>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>     In file included from include/linux/virtio.h:12,
>                      from include/linux/virtio_config.h:7,
>                      from include/uapi/linux/virtio_net.h:30,
>                      from include/linux/virtio_net.h:6,
>                      from net//packet/af_packet.c:82:
>>> include/linux/vringh.h:18:10: fatal error: linux/vhost_iotlb.h: No such file or directory
>        18 | #include <linux/vhost_iotlb.h>
>           |          ^~~~~~~~~~~~~~~~~~~~~
>     compilation terminated.
>
> vim +18 include/linux/vringh.h
>
>    > 18	#include <linux/vhost_iotlb.h>
>      19	#include <asm/barrier.h>
>      20	


I can hardly believe it can't work.

I get

# file include/linux/vringh.h
include/linux/vringh.h: C source, ASCII text

So this looks like a false positive to me?

Thanks


>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


  reply	other threads:[~2020-03-30  2:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 12:08 [vhost:linux-next 8/13] include/linux/vringh.h:18:10: fatal error: linux/vhost_iotlb.h: No such file or directory kbuild test robot
2020-03-30  2:46 ` Jason Wang [this message]
2020-03-31  7:31   ` Xia, Hui
2020-03-31  8:10     ` Jason Wang

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=f1270de5-7a2c-76d2-431c-34364def851a@redhat.com \
    --to=jasowang@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).