[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFw80CuJG6HYgHfsw-Tt8k5KpOOQSpOs0xyLQnZy5uxHrg@mail.gmail.com>
Date: Mon, 31 Mar 2014 19:26:28 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andi Kleen <ak@...ux.intel.com>
Cc: "H. Peter Anvin" <hpa@...ux.intel.com>,
Gleb Natapov <gleb@...hat.com>, Peter Anvin <hpa@...or.com>,
Jan Hubicka <hubicka@....cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Jaroslav Kysela <perex@...ex.cz>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Rusty Russell <rusty@...tcorp.com.au>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [GIT PULL] x86 LTO changes for v3.15
On Mon, Mar 31, 2014 at 6:09 PM, Andi Kleen <ak@...ux.intel.com> wrote:
>
> I think SYSCALL_DEFINE actually doesn't need it, as the syscall
> tables are visible in C. Only the syscall table itself
> needs to be visible.
Ahh, good point. The table used to be in asm for x86-32, but that got
fixed long ago so I guess that just isn't an issue any more.
>> and after that I strongly suspect that there will be only a handful of
>> cases left that are called from assembly language and that aren't
>> system calls. Things like "printk()" and friends that are really
>> special. They'd need a few manual "__visible" annotations.
>
> Ok. I think it's more than a handful though.
I guess an allmodconfig build with the LTO binutils should just
generate linker errors for all of them, so they should be easy to
find, though?
Linus
--
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