All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Gong" <gong.chen@linux.intel.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
	Michel Lespinasse <walken@google.com>,
	Seiji Aguchi <seiji.aguchi@hds.com>,
	Yang Zhang <yang.z.zhang@Intel.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Janet Morgan <janet.morgan@Intel.com>,
	Tony Luck <tony.luck@Intel.com>, Ruiv Wang <ruiv.wang@gmail.com>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	x86@kernel.org, Fengguang Wu <fengguang.wu@Intel.com>
Subject: Re: [PATCH] x86, cpu hotplug, use cpumask stack safe variant cpumask_var_t in check_irq_vectors_for_cpu_disable() [v2]
Date: Tue, 21 Jan 2014 21:00:49 -0500	[thread overview]
Message-ID: <20140122020049.GA16393@gchen.bj.intel.com> (raw)
In-Reply-To: <1390244278-30024-1-git-send-email-prarit@redhat.com>

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

On Mon, Jan 20, 2014 at 01:57:58PM -0500, Prarit Bhargava wrote:
> Subject: [PATCH] x86, cpu hotplug, use cpumask stack safe variant
>  cpumask_var_t in check_irq_vectors_for_cpu_disable() [v2]
> 
> kbuild, 0day kernel build service, outputs the warning:
> 
> arch/x86/kernel/irq.c:333:1: warning: the frame size of 2056 bytes
> is larger than 2048 bytes [-Wframe-larger-than=]
> 
> because check_irq_vectors_for_cpu_disable() allocates two cpumasks on the
> stack.  Fix this by using cpumask_var_t, the cpumask stack safe variant.
> 
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: Michel Lespinasse <walken@google.com>
> Cc: Seiji Aguchi <seiji.aguchi@hds.com>
> Cc: Yang Zhang <yang.z.zhang@Intel.com>
> Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
> Cc: Janet Morgan <janet.morgan@intel.com>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Ruiv Wang <ruiv.wang@gmail.com>
> Cc: Gong Chen <gong.chen@linux.intel.com>
> Cc: H. Peter Anvin <hpa@linux.intel.com>
> Cc: Gong Chen <gong.chen@linux.intel.com>
> Cc: x86@kernel.org
> Cc: Fengguang Wu <fengguang.wu@intel.com>
> 
> [v2]: switch from GFP_KERNEL to GFP_ATOMIC

Reviewed-by: Chen, Gong <gong.chen@linux.intel.com>


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2014-01-22  2:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 13:39 [PATCH] x86, cpu hotplug, use cpumask stack safe variant cpumask_var_t in check_irq_vectors_for_cpu_disable() Prarit Bhargava
2014-01-20  8:50 ` Chen, Gong
2014-01-20 18:57   ` [PATCH] x86, cpu hotplug, use cpumask stack safe variant cpumask_var_t in check_irq_vectors_for_cpu_disable() [v2] Prarit Bhargava
2014-01-22  2:00     ` Chen, Gong [this message]

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=20140122020049.GA16393@gchen.bj.intel.com \
    --to=gong.chen@linux.intel.com \
    --cc=ak@linux.intel.com \
    --cc=fengguang.wu@Intel.com \
    --cc=hpa@linux.intel.com \
    --cc=janet.morgan@Intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=prarit@redhat.com \
    --cc=ruiv.wang@gmail.com \
    --cc=seiji.aguchi@hds.com \
    --cc=tony.luck@Intel.com \
    --cc=walken@google.com \
    --cc=x86@kernel.org \
    --cc=yang.z.zhang@Intel.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.