From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: tim.gardner@canonical.com, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4.4-rc8 1/4] x86/microcode/intel: save_mc_for_early: Squelch frame size warning
Date: Wed, 9 Mar 2016 13:41:17 +0100 [thread overview]
Message-ID: <20160309124117.GA26069@gmail.com> (raw)
In-Reply-To: <20160118101004.GC12644@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> On Thu, Jan 07, 2016 at 07:59:56AM -0700, tim.gardner@canonical.com wrote:
> > From: Tim Gardner <tim.gardner@canonical.com>
> >
> > arch/x86/kernel/cpu/microcode/intel.c: In function 'save_mc_for_early':
> > arch/x86/kernel/cpu/microcode/intel.c:516:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
>
> Ok, so this looks like a 32-bit warning to me.
>
> Hmm, so, on the one hand we do have:
>
> $ git grep CONFIG_FRAME_WARN arch/x86/
> arch/x86/configs/i386_defconfig:291:CONFIG_FRAME_WARN=2048
>
> which came in with:
>
> 5cb04df8d3f0 ("x86: defconfig updates")
>
> and OTOH:
>
> config FRAME_WARN
> int "Warn for stack frames larger than (needs gcc 4.4)"
> range 0 8192
> default 0 if KASAN
> default 1024 if !64BIT
> ^^^^
>
> default 2048 if 64BIT
> help
> Tell gcc to warn at build time for stack frames larger than this.
> Setting this too low will cause a lot of warnings.
> Setting it to 0 disables the warning.
> Requires gcc 4.4
>
> which is still 1024.
>
> tip guys, maybe it is time to update lib/Kconfig.debug too?
I think we should rather update the 32-bit defconfig? 64-bit stacks are more
generous, and a 2K stack footprint is pretty extreme on 32-bit I think ...
Thanks,
Ingo
next prev parent reply other threads:[~2016-03-09 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 14:59 [PATCH v4.4-rc8 0/4] x86/microcode/intel: Squelch frame size warnings tim.gardner
2016-01-07 14:59 ` [PATCH v4.4-rc8 1/4] x86/microcode/intel: save_mc_for_early: Squelch frame size warning tim.gardner
2016-01-18 10:10 ` Borislav Petkov
2016-03-09 12:41 ` Ingo Molnar [this message]
2016-03-09 13:47 ` Borislav Petkov
2016-03-09 13:48 ` [PATCH] x86/i386-defconfig: Set CONFIG_FRAME_WARN to Kconfig default Borislav Petkov
2016-03-09 13:58 ` [tip:x86/build] x86/defconfigs/32: Set CONFIG_FRAME_WARN to the " tip-bot for Borislav Petkov
2016-01-07 14:59 ` [PATCH v4.4-rc8 2/4] x86/microcode/intel: save_microcode_in_initrd_intel: Squelch frame size warning tim.gardner
2016-01-07 14:59 ` [PATCH v4.4-rc8 3/4] x86/microcode/intel: load_microcode: " tim.gardner
2016-01-07 14:59 ` [PATCH v4.4-rc8 4/4] x86/microcode/intel: get_matching_model_microcode: " tim.gardner
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=20160309124117.GA26069@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tim.gardner@canonical.com \
--cc=x86@kernel.org \
/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.