Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752566AbXLDXPd (ORCPT ); Tue, 4 Dec 2007 18:15:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751309AbXLDXPZ (ORCPT ); Tue, 4 Dec 2007 18:15:25 -0500 Received: from mailout.stusta.mhn.de ([141.84.69.5]:41011 "EHLO mailhub.stusta.mhn.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751055AbXLDXPY (ORCPT ); Tue, 4 Dec 2007 18:15:24 -0500 Date: Wed, 5 Dec 2007 00:15:19 +0100 From: Adrian Bunk To: Harvey Harrison Cc: Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner , LKML Subject: Re: [RFC PATCH] x86: Unify include/asm-x86/linkage_[32|64].h Message-ID: <20071204231519.GI15974@stusta.de> References: <1196801629.10408.26.camel@brick> <20071204213247.GA11216@elte.hu> <1196806868.10408.33.camel@brick> <20071204222717.GA25974@elte.hu> <20071204224543.GH15974@stusta.de> <1196809075.10408.42.camel@brick> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1196809075.10408.42.camel@brick> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2331 Lines: 55 On Tue, Dec 04, 2007 at 02:57:55PM -0800, Harvey Harrison wrote: > > On Tue, 2007-12-04 at 23:45 +0100, Adrian Bunk wrote: > > On Tue, Dec 04, 2007 at 11:27:17PM +0100, Ingo Molnar wrote: > > > > > > * Harvey Harrison wrote: > > > > > > > On Tue, 2007-12-04 at 22:32 +0100, Ingo Molnar wrote: > > > > > * Harvey Harrison wrote: > > > > > > > > > > > I'm not sure if the definition of asmlinkage and prevent_tail_call can > > > > > > be omitted as well and let the linux/linkage.h version get picked up > > > > > > instead. > > > > > > > > > > no, we cannot remove them - asmlinkage is needed for the syscall > > > > > entry (and other entry code) to work, the and the prevent_tail_call > > > > > works around a compiler bug. (which might or might not be fixed in > > > > > latest gcc - but we generally dont remove workarounds unless we are > > > > > really sure it's fine.) > > > > > > > > OK, but if this patch is acceptable, then there is no more places in > > > > the tree that define the FASTCALL macro, other than the empty default > > > > in include/linux/linkage.h. So I think a second step would be to > > > > start to get rid of FASTCALL callers elsewhere in the tree...thoughts? > > > > > > the removal of FASTCALL is fine: the default (and only) compiler model > > > for x86 (32-bit) is regparm(3), so the regparm(3) macro is equivalent to > > > the empty one in linux/linkage.h. > > >... > > > > But please ensure that they stay in assembler code also used by UML. > > I'm curious how UML is using FASTCALL/fastcall. Any pointers? UML can't switch to the regparm(3) convention on i386 since it links with userspace code, so if assembler code uses this calling convention we need the C prototype of it annotated accordingly. > Harvey cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/