public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: kbuild test robot <lkp@intel.com>
Cc: Ming Lei <ming.lei@redhat.com>,
	kbuild-all@01.org, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Laurence Oberman <loberman@redhat.com>
Subject: Re: [PATCH V2 3/5] genirq/affinity: move actual irq vector spread into one helper
Date: Wed, 7 Mar 2018 23:48:59 -0800	[thread overview]
Message-ID: <20180308074859.GA17098@infradead.org> (raw)
In-Reply-To: <201803060052.L1IpJHee%fengguang.wu@intel.com>

Can you fix this up and resend?

On Tue, Mar 06, 2018 at 12:28:32AM +0800, kbuild test robot wrote:
> Hi Ming,
> 
> Thank you for the patch! Perhaps something to improve:
> 
> [auto build test WARNING on tip/irq/core]
> [also build test WARNING on v4.16-rc4 next-20180305]
> [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/Ming-Lei/genirq-affinity-irq-vector-spread-among-online-CPUs-as-far-as-possible/20180305-184912
> config: i386-randconfig-a1-201809 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> 
> All warnings (new ones prefixed by >>):
> 
>    kernel/irq/affinity.c: In function 'irq_create_affinity_masks':
> >> kernel/irq/affinity.c:201:50: warning: passing argument 3 of 'irq_build_affinity_masks' from incompatible pointer type
>      curvec += irq_build_affinity_masks(nvecs, affd, node_to_cpumask,
>                                                      ^
>    kernel/irq/affinity.c:97:12: note: expected 'const struct cpumask (*)[1]' but argument is of type 'struct cpumask (*)[1]'
>     static int irq_build_affinity_masks(int nvecs, const struct irq_affinity *affd,
>                ^
> 
> vim +/irq_build_affinity_masks +201 kernel/irq/affinity.c
> 
>    161	
>    162	/**
>    163	 * irq_create_affinity_masks - Create affinity masks for multiqueue spreading
>    164	 * @nvecs:	The total number of vectors
>    165	 * @affd:	Description of the affinity requirements
>    166	 *
>    167	 * Returns the masks pointer or NULL if allocation failed.
>    168	 */
>    169	struct cpumask *
>    170	irq_create_affinity_masks(int nvecs, const struct irq_affinity *affd)
>    171	{
>    172		int curvec;
>    173		struct cpumask *masks;
>    174		cpumask_var_t nmsk, *node_to_cpumask;
>    175	
>    176		/*
>    177		 * If there aren't any vectors left after applying the pre/post
>    178		 * vectors don't bother with assigning affinity.
>    179		 */
>    180		if (nvecs == affd->pre_vectors + affd->post_vectors)
>    181			return NULL;
>    182	
>    183		if (!zalloc_cpumask_var(&nmsk, GFP_KERNEL))
>    184			return NULL;
>    185	
>    186		masks = kcalloc(nvecs, sizeof(*masks), GFP_KERNEL);
>    187		if (!masks)
>    188			goto out;
>    189	
>    190		node_to_cpumask = alloc_node_to_cpumask();
>    191		if (!node_to_cpumask)
>    192			goto out;
>    193	
>    194		/* Fill out vectors at the beginning that don't need affinity */
>    195		for (curvec = 0; curvec < affd->pre_vectors; curvec++)
>    196			cpumask_copy(masks + curvec, irq_default_affinity);
>    197	
>    198		/* Stabilize the cpumasks */
>    199		get_online_cpus();
>    200		build_node_to_cpumask(node_to_cpumask);
>  > 201		curvec += irq_build_affinity_masks(nvecs, affd, node_to_cpumask,
>    202						   cpu_possible_mask, nmsk, masks);
>    203		put_online_cpus();
>    204	
>    205		/* Fill out vectors at the end that don't need affinity */
>    206		for (; curvec < nvecs; curvec++)
>    207			cpumask_copy(masks + curvec, irq_default_affinity);
>    208		free_node_to_cpumask(node_to_cpumask);
>    209	out:
>    210		free_cpumask_var(nmsk);
>    211		return masks;
>    212	}
>    213	
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation


---end quoted text---

  reply	other threads:[~2018-03-08  7:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  3:13 [PATCH V2 0/5] genirq/affinity: irq vector spread among online CPUs as far as possible Ming Lei
2018-03-05  3:13 ` [PATCH V2 1/5] genirq/affinity: rename *node_to_possible_cpumask as *node_to_cpumask Ming Lei
2018-03-05  3:13 ` [PATCH V2 2/5] genirq/affinity: mark 'node_to_cpumask' as const for get_nodes_in_cpumask() Ming Lei
2018-03-05  3:13 ` [PATCH V2 3/5] genirq/affinity: move actual irq vector spread into one helper Ming Lei
2018-03-05 16:28   ` kbuild test robot
2018-03-08  7:48     ` Christoph Hellwig [this message]
2018-03-08 10:05     ` Ming Lei
2018-03-05  3:13 ` [PATCH V2 4/5] genirq/affinity: support to do irq vectors spread starting from any vector Ming Lei
2018-03-05  3:13 ` [PATCH V2 5/5] genirq/affinity: irq vector spread among online CPUs as far as possible Ming Lei

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=20180308074859.GA17098@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=kbuild-all@01.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=loberman@redhat.com \
    --cc=ming.lei@redhat.com \
    --cc=tglx@linutronix.de \
    /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