Linux virtualization list
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: kvm@vger.kernel.org, mst@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, peterx@redhat.com,
	virtualization@lists.linux-foundation.org,
	maxime.coquelin@redhat.com, kbuild-all@01.org,
	vkaplans@redhat.com, wexu@redhat.com
Subject: Re: [PATCH] vhost: introduce O(1) vq metadata cache
Date: Wed, 14 Dec 2016 16:14:59 +0800	[thread overview]
Message-ID: <201612141605.QJowNf4i%fengguang.wu@intel.com> (raw)
In-Reply-To: <1481702183-16088-1-git-send-email-jasowang@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]

Hi Jason,

[auto build test WARNING on vhost/linux-next]
[also build test WARNING on v4.9 next-20161214]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Jason-Wang/vhost-introduce-O-1-vq-metadata-cache/20161214-160153
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
config: i386-randconfig-x005-201650 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   drivers/vhost/vhost.c: In function 'vhost_vq_meta_fetch':
>> drivers/vhost/vhost.c:719:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
     return (void *)(node->userspace_addr + (u64)addr - node->start);
            ^

vim +719 drivers/vhost/vhost.c

   703							   node->start,
   704							   node->size))
   705				return 0;
   706		}
   707		return 1;
   708	}
   709	
   710	static inline void __user *vhost_vq_meta_fetch(struct vhost_virtqueue *vq,
   711						       u64 addr, unsigned int size,
   712						       int type)
   713	{
   714		const struct vhost_umem_node *node = vq->meta_iotlb[type];
   715	
   716		if (!node)
   717			return NULL;
   718	
 > 719		return (void *)(node->userspace_addr + (u64)addr - node->start);
   720	}
   721	
   722	/* Can we switch to this memory table? */
   723	/* Caller should have device mutex but not vq mutex */
   724	static int memory_access_ok(struct vhost_dev *d, struct vhost_umem *umem,
   725				    int log_all)
   726	{
   727		int i;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27829 bytes --]

[-- Attachment #3: Type: text/plain, Size: 183 bytes --]

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2016-12-14  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  7:56 [PATCH] vhost: introduce O(1) vq metadata cache Jason Wang
2016-12-14  8:14 ` kbuild test robot [this message]
2016-12-14  9:33   ` 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=201612141605.QJowNf4i%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=jasowang@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=vkaplans@redhat.com \
    --cc=wexu@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