From: "Michael S. Tsirkin" <mst@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
kbuild-all@01.org, netdev@vger.kernel.org, davem@davemloft.net,
jasowang@redhat.com, den@klaipeden.com,
virtualization@lists.linux-foundation.org,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next] vhost_net: do not stall on zerocopy depletion
Date: Sun, 1 Oct 2017 06:20:49 +0300 [thread overview]
Message-ID: <20171001062018-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <201710010753.KeY9a5xF%fengguang.wu@intel.com>
On Sun, Oct 01, 2017 at 08:09:30AM +0800, kbuild test robot wrote:
> Hi Willem,
>
> [auto build test WARNING on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Willem-de-Bruijn/vhost_net-do-not-stall-on-zerocopy-depletion/20171001-054709
> reproduce:
> # apt-get install sparse
> make ARCH=x86_64 allmodconfig
> make C=1 CF=-D__CHECK_ENDIAN__
BTW __CHECK_ENDIAN__ is the default now, I think you can drop it from
your scripts.
>
> sparse warnings: (new ones prefixed by >>)
>
>
> vim +440 drivers/vhost/net.c
>
> 433
> 434 static bool vhost_exceeds_maxpend(struct vhost_net *net)
> 435 {
> 436 struct vhost_net_virtqueue *nvq = &net->vqs[VHOST_NET_VQ_TX];
> 437 struct vhost_virtqueue *vq = &nvq->vq;
> 438
> 439 return (nvq->upend_idx + UIO_MAXIOV - nvq->done_idx) % UIO_MAXIOV >
> > 440 min(VHOST_MAX_PEND, vq->num >> 2);
> 441 }
> 442
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2017-10-01 3:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 0:25 [PATCH net-next] vhost_net: do not stall on zerocopy depletion Willem de Bruijn
2017-09-28 0:33 ` Willem de Bruijn
2017-09-28 0:33 ` Willem de Bruijn
2017-09-28 7:41 ` Jason Wang
2017-09-28 7:41 ` Jason Wang
2017-09-28 16:05 ` Willem de Bruijn
2017-09-28 16:05 ` Willem de Bruijn
2017-09-29 19:38 ` Michael S. Tsirkin
2017-09-29 19:38 ` Michael S. Tsirkin
2017-09-30 1:25 ` Willem de Bruijn
2017-10-02 4:08 ` Michael S. Tsirkin
2017-10-02 4:08 ` Michael S. Tsirkin
2017-10-02 21:34 ` Willem de Bruijn
2017-10-02 21:34 ` Willem de Bruijn
2017-09-30 1:25 ` Willem de Bruijn
2017-09-30 22:12 ` kbuild test robot
2017-09-30 22:20 ` kbuild test robot
2017-09-30 22:20 ` kbuild test robot
2017-10-01 0:09 ` kbuild test robot
2017-10-01 0:09 ` kbuild test robot
2017-10-01 3:20 ` Michael S. Tsirkin [this message]
2017-10-01 3:26 ` [kbuild-all] " Fengguang Wu
2017-10-01 3:26 ` Fengguang Wu
2017-10-01 3:20 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2017-09-28 0:25 Willem de Bruijn
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=20171001062018-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=den@klaipeden.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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 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.