[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <556F2A37.9020102@amd.com>
Date: Wed, 3 Jun 2015 11:24:23 -0500
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
To: Borislav Petkov <bp@...en8.de>
CC: <dougthompson@...ssion.com>, <mchehab@....samsung.com>,
<linux-edac@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<x86@...nel.org>
Subject: Re: [PATCH V2 3/9] edac, mce_amd_inj: Modify flags attrigute to use
string arguments
On 6/3/2015 11:00 AM, Borislav Petkov wrote:
> On Wed, Jun 03, 2015 at 10:34:50AM -0500, Aravind Gopalakrishnan wrote:
>> Oddly, No. The only thing I got was:
>> arch/x86/kernel/cpu/microcode/intel_early.c: In function
>> âget_matching_model_microcode.isra.2.constprop.7â:
>> arch/x86/kernel/cpu/microcode/intel_early.c:348:1: warning: the frame size
>> of 1064 bytes is larger than 1024 bytes [-Wframe-larger-than=]
>> }
>> ^
> 32-bit?
>
> Because on 64-bit, that frame size is relaxed to 2K.
>
> config FRAME_WARN
> int "Warn for stack frames larger than (needs gcc 4.4)"
> range 0 8192
> default 1024 if !64BIT
> default 2048 if 64BIT
>
Nope. But it's still set to 1K for me, and I think I know where the
problem might have originated from..
I used a generic distro (Ubuntu) config as base when I first built the
kernel,
and I see that on Ubuntu's 'generic' configs, the value for FRAME_WARN
is 1K.
(Btw, I did install a 64-bit version of the distro on the system to
begin with.. guess they just set it to 1K always)
When I do make defconfig, this is set to 2K properly.
Thanks,
-Aravind
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists