From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Binutils <binutils@sourceware.org>,
Andy Lutomirski <luto@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [committed, PATCH] Add -mshared option to x86 ELF assembler
Date: Tue, 2 Jun 2015 09:41:12 +0200 [thread overview]
Message-ID: <20150602074112.GA8005@gmail.com> (raw)
In-Reply-To: <CALCETrUsp+B1SZAj7v4U1aYQKkaisMbSeSg2yevHXGJyTQcM=g@mail.gmail.com>
* Andy Lutomirski <luto@amacapital.net> wrote:
> On Mon, Jun 1, 2015 at 4:05 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> > On Mon, Jun 1, 2015 at 1:32 AM, Markus Trippelsdorf
> > <markus@trippelsdorf.de> wrote:
> >> On 2015.05.15 at 03:34 -0700, H.J. Lu wrote:
> >>> This patch adds -mshared option to x86 ELF assembler. By default,
> >>> assembler will optimize out non-PLT relocations against defined non-weak
> >>> global branch targets with default visibility. The -mshared option tells
> >>> the assembler to generate code which may go into a shared library
> >>> where all non-weak global branch targets with default visibility can
> >>> be preempted. The resulting code is slightly bigger. This option
> >>> only affects the handling of branch instructions.
> >>>
> >>> This Linux kernel patch is needed to create a working x86 Linux kernel if
> >>> it hasn't been applied:
> >>>
> >>> diff --git a/arch/x86/kernel/head_64.S b/arch/x86/kernel/head_64.S
> >>> index ae6588b..b91a00c 100644
> >>> --- a/arch/x86/kernel/head_64.S
> >>> +++ b/arch/x86/kernel/head_64.S
> >>> @@ -339,8 +339,8 @@ early_idt_handlers:
> >>> i = i + 1
> >>> .endr
> >>>
> >>> -/* This is global to keep gas from relaxing the jumps */
> >>> -ENTRY(early_idt_handler)
> >>> +/* This is weak to keep gas from relaxing the jumps */
> >>> +WEAK(early_idt_handler)
> >>> cld
> >>
> >> Have you posted the patch to LKML already?
> >> (I hit this issue today and it took me a while to figure out the cause.)
> >
> > A kernel patch will be checked in soon.
> >
>
> It already is:
>
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=x86/asm&id=cdeb6048940fa4bfb429e2f1cba0d28a11e20cd5
>
> It's currently queued for 4.2.
>
> Ingo, would it make sense to promote this to 4.1? It's definitely a violation
> of the "no development after the merge window" rule, but it's sort of a build
> fix. [...]
Yeah, agreed - the commit was problem-free in testing, so I've cherry-picked it
over into tip:x86/urgent and will push it to Linus for v4.1.
Thanks,
Ingo
prev parent reply other threads:[~2015-06-02 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150515103414.GA20518@intel.com>
[not found] ` <20150601083214.GA381@x4>
[not found] ` <CAMe9rOrdqc1v7Dzm3T=CO2a7mVNypOXkAZMFxRMJwwcu61jxGQ@mail.gmail.com>
2015-06-01 15:48 ` [committed, PATCH] Add -mshared option to x86 ELF assembler Andy Lutomirski
2015-06-02 7:41 ` Ingo Molnar [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=20150602074112.GA8005@gmail.com \
--to=mingo@kernel.org \
--cc=binutils@sourceware.org \
--cc=gregkh@linuxfoundation.org \
--cc=hjl.tools@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=markus@trippelsdorf.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