linux-kernel - Re: [RFC 0/6] x86 tip asm ENTRY,ENDPROC cleanup

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]

Date:	Fri, 13 Feb 2009 16:34:00 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alexander van Heukelum <heukelum@...tmail.fm>
CC:	Cyrill Gorcunov <gorcunov@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Jan Beulich <jbeulich@...ell.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/6] x86 tip asm ENTRY,ENDPROC cleanup

Alexander van Heukelum wrote:
> 
> Hi Cyrill,
> 
> I like this direction. If I understand correctly:
> 
> ENTRY/END or GLOBAL/END for data.
> ENTRY/ENDPROC or GLOBAL/ENDPROC for functions.
> 

Fine for functions, but it's really not okay to use the same macros for 
data.  Furthermore, we need to consider special entry points that don't 
behave like normal functions -- like system call or interrupt entry.

Why?  Because if we're compiling with frame pointers, we would like the 
wrapper macros for functions to handle setting up and tearing down the 
frame pointer, at least in the common case.

	-hpa
--
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/