From: kbuild test robot <lkp@intel.com>
To: Caleb Raitto <caraitto@google.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: [net-next:master 1999/2033] drivers//net/virtio_net.c:1916:10: error: implicit declaration of function 'cpumask_next_wrap'; did you mean 'cpumask_next_and'?
Date: Sun, 12 Aug 2018 07:11:30 +0800 [thread overview]
Message-ID: <201808120728.OuaIsUfg%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2533 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 9a95d9c6429bb58905fdfc95da2e1b7cc3fb55b7
commit: 2ca653d607ce59f2729173a7ea56dbfa6330ec88 [1999/2033] virtio_net: Stripe queue affinities across cores.
config: sh-allyesconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.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 2ca653d607ce59f2729173a7ea56dbfa6330ec88
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=sh
All errors (new ones prefixed by >>):
drivers//net/virtio_net.c: In function 'virtnet_set_affinity':
>> drivers//net/virtio_net.c:1916:10: error: implicit declaration of function 'cpumask_next_wrap'; did you mean 'cpumask_next_and'? [-Werror=implicit-function-declaration]
cpu = cpumask_next_wrap(cpu, cpu_online_mask,
^~~~~~~~~~~~~~~~~
cpumask_next_and
cc1: some warnings being treated as errors
vim +1916 drivers//net/virtio_net.c
1889
1890 static void virtnet_set_affinity(struct virtnet_info *vi)
1891 {
1892 cpumask_var_t mask;
1893 int stragglers;
1894 int group_size;
1895 int i, j, cpu;
1896 int num_cpu;
1897 int stride;
1898
1899 if (!zalloc_cpumask_var(&mask, GFP_KERNEL)) {
1900 virtnet_clean_affinity(vi, -1);
1901 return;
1902 }
1903
1904 num_cpu = num_online_cpus();
1905 stride = max_t(int, num_cpu / vi->curr_queue_pairs, 1);
1906 stragglers = num_cpu >= vi->curr_queue_pairs ?
1907 num_cpu % vi->curr_queue_pairs :
1908 0;
1909 cpu = cpumask_next(-1, cpu_online_mask);
1910
1911 for (i = 0; i < vi->curr_queue_pairs; i++) {
1912 group_size = stride + (i < stragglers ? 1 : 0);
1913
1914 for (j = 0; j < group_size; j++) {
1915 cpumask_set_cpu(cpu, mask);
> 1916 cpu = cpumask_next_wrap(cpu, cpu_online_mask,
1917 nr_cpu_ids, false);
1918 }
1919 virtqueue_set_affinity(vi->rq[i].vq, mask);
1920 virtqueue_set_affinity(vi->sq[i].vq, mask);
1921 __netif_set_xps_queue(vi->dev, cpumask_bits(mask), i, false);
1922 cpumask_clear(mask);
1923 }
1924
1925 vi->affinity_hint_set = true;
1926 free_cpumask_var(mask);
1927 }
1928
---
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: 49014 bytes --]
reply other threads:[~2018-08-12 1:47 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=201808120728.OuaIsUfg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=caraitto@google.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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