From: Matthias Kaehlcke <mka@chromium.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
"H . J . Lu" <hjl.tools@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Michael Davidson <md@google.com>,
Greg Hackmann <ghackmann@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Stephen Hines <srhines@google.com>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
Bernhard.Rosenkranzer@linaro.org,
Peter Foley <pefoley2@pefoley.com>,
Behan Webster <behanw@converseincode.com>,
Douglas Anderson <dianders@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] x86/build: Specify stack alignment for clang
Date: Mon, 12 Jun 2017 09:17:14 -0700 [thread overview]
Message-ID: <20170612161714.GI141096@google.com> (raw)
In-Reply-To: <20170610070359.7pci2anwe3pvvcea@gmail.com>
El Sat, Jun 10, 2017 at 09:03:59AM +0200 Ingo Molnar ha dit:
>
> * Matthias Kaehlcke <mka@chromium.org> wrote:
>
> > For gcc stack alignment is configured with -mpreferred-stack-boundary=N,
> > clang has the option -mstack-alignment=N for that purpose. Use the same
> > alignment as for gcc.
> >
> > If the alignment is not specified clang assumes an alignment of 16 bytes,
> > as required by the standard ABI. However as mentioned in d9b0cde91c60
> > ("x86-64, gcc: Use -mpreferred-stack-boundary=3 if supported") the
> > standard kernel entry on x86-64 leaves the stack on an 8-byte
> > boundary, as a consequence clang will keep the stack misaligned.
> >
> > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> > ---
> > arch/x86/Makefile | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/x86/Makefile b/arch/x86/Makefile
> > index 5851411e60fb..a32badbe87ad 100644
> > --- a/arch/x86/Makefile
> > +++ b/arch/x86/Makefile
> > @@ -27,7 +27,8 @@ REALMODE_CFLAGS := $(M16_CFLAGS) -g -Os -D__KERNEL__ \
> > -mno-mmx -mno-sse \
> > $(call cc-option, -ffreestanding) \
> > $(call cc-option, -fno-stack-protector) \
> > - $(call cc-option, -mpreferred-stack-boundary=2)
> > + $(call cc-option, -mpreferred-stack-boundary=2) \
> > + $(call cc-option, -mstack-alignment=2)
> > export REALMODE_CFLAGS
> >
> > # BITS is used as extension for files which are available in a 32 bit
> > @@ -64,8 +65,9 @@ ifeq ($(CONFIG_X86_32),y)
> > # with nonstandard options
> > KBUILD_CFLAGS += -fno-pic
> >
> > - # prevent gcc from keeping the stack 16 byte aligned
> > + # prevent the compiler from keeping the stack 16 byte aligned
> > KBUILD_CFLAGS += $(call cc-option,-mpreferred-stack-boundary=2)
> > + KBUILD_CFLAGS += $(call cc-option,-mstack-alignment=2)
> >
> > # Disable unit-at-a-time mode on pre-gcc-4.0 compilers, it makes gcc use
> > # a lot more stack due to the lack of sharing of stacklots:
> > @@ -97,8 +99,9 @@ else
> > KBUILD_CFLAGS += $(call cc-option,-mno-80387)
> > KBUILD_CFLAGS += $(call cc-option,-mno-fp-ret-in-387)
> >
> > - # Use -mpreferred-stack-boundary=3 if supported.
> > + # Align the stack to 8 bytes if supported.
> > KBUILD_CFLAGS += $(call cc-option,-mpreferred-stack-boundary=3)
> > + KBUILD_CFLAGS += $(call cc-option,-mstack-alignment=3)
> >
> > # Use -mskip-rax-setup if supported.
> > KBUILD_CFLAGS += $(call cc-option,-mskip-rax-setup)
>
> That's really ugly and the duplicated options are repeated. A cleaner solution
> would be introduce a variable that stores the option, and use that later on. Also
> describe the variable, pointing out that -mpreferred-stack-boundary is a GCC
> option, while -mstack-alignment is a Clang one.
Thanks for your comments, I will send out an updated patch shortly.
next prev parent reply other threads:[~2017-06-12 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 17:31 [PATCH] x86/build: Specify stack alignment for clang Matthias Kaehlcke
2017-06-10 7:03 ` Ingo Molnar
2017-06-12 16:17 ` Matthias Kaehlcke [this message]
2017-06-12 18:34 ` Matthias Kaehlcke
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=20170612161714.GI141096@google.com \
--to=mka@chromium.org \
--cc=Bernhard.Rosenkranzer@linaro.org \
--cc=a.p.zijlstra@chello.nl \
--cc=arnd@arndb.de \
--cc=behanw@converseincode.com \
--cc=dianders@chromium.org \
--cc=ghackmann@google.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=pefoley2@pefoley.com \
--cc=srhines@google.com \
--cc=tglx@linutronix.de \
--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