From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Borislav Petkov <bp@alien8.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH] x86/fpu: Fix boot crash in the early FPU code
Date: Sun, 5 Jul 2015 11:00:14 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.11.1507051049480.31060@eddie.linux-mips.org> (raw)
In-Reply-To: <20150704075819.GA9201@gmail.com>
On Sat, 4 Jul 2015, Ingo Molnar wrote:
> Btw., is it a GCC bug or a known GCC property that a structure with a 16-byte
> alignment attribute does not get properly aligned on the stack?
What's the stack alignment mandated by the x86 psABI? Is that anything
beyond what the PUSH instructions imply (i.e. 4 bytes for 32-bit and 8
bytes for 64-bit targets)? Otherwise GCC might not be smart enough to
apply the right subtract and mask operations to the stack/frame pointer.
This might even have been documented with the alignment attribute.
> So fix this bug by making the variable static again, but also mark it
> __initdata this time, because fpu__init_system_mxcsr() is now an
> __init function.
You could have used `alloca' and manually aligned the structure within
the area obtained too (to avoid static storage if desired).
FWIW,
Maciej
next prev parent reply other threads:[~2015-07-05 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 15:23 Non-booting current Linus' tree Jan Kara
2015-07-03 15:28 ` Thomas Gleixner
2015-07-03 21:40 ` Linus Torvalds
2015-07-04 7:58 ` [PATCH] x86/fpu: Fix boot crash in the early FPU code Ingo Molnar
2015-07-04 8:07 ` Thomas Gleixner
2015-07-04 8:08 ` Ingo Molnar
2015-07-04 8:09 ` [tip:x86/urgent] " tip-bot for Ingo Molnar
2015-07-05 10:00 ` Maciej W. Rozycki [this message]
2015-07-05 20:01 ` Non-booting current Linus' tree Andy Lutomirski
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=alpine.LFD.2.11.1507051049480.31060@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=bp@alien8.de \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®