linux-kernel - Re: [PATCH] x86/asm/entry/64/compat: Rename ia32entry.S -> entry_64_compat

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMzpN2jU-gZLbu6hedjAj32pgZ7y=LfNQM-g_u-=z1npZJ8xhw@mail.gmail.com>
Date:	Fri, 5 Jun 2015 10:02:04 -0400
From:	Brian Gerst <brgerst@...il.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andy Lutomirski <luto@...capital.net>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...en8.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/asm/entry/64/compat: Rename ia32entry.S -> entry_64_compat_32.S

On Fri, Jun 5, 2015 at 9:00 AM, Ingo Molnar <mingo@...nel.org> wrote:
> So we now have the following system entry code related
> files, which define the following system call instruction
> and other entry paths:
>
>    entry_32.S            # 32-bit binaries on 32-bit kernels
>    entry_64.S            # 64-bit binaries on 64-bit kernels
>    entry_64_compat_32.S  # 32-bit binaries on 64-bit kernels

That's too long.  How about just merging it into entry_64.S?  That
could also allow moving some of the obscure macros from calling.h into
entry_64.S where they are more visible.

--
Brian Gerst
--
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/