From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263472AbUJ3BiL (ORCPT ); Fri, 29 Oct 2004 21:38:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261571AbUJ2TiR (ORCPT ); Fri, 29 Oct 2004 15:38:17 -0400 Received: from fw.osdl.org ([65.172.181.6]:29635 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S261477AbUJ2SzH (ORCPT ); Fri, 29 Oct 2004 14:55:07 -0400 Date: Fri, 29 Oct 2004 11:54:57 -0700 (PDT) From: Linus Torvalds To: linux-os@analogic.com cc: Richard Henderson , Kernel Mailing List , Andi Kleen , Andrew Morton , Jan Hubicka Subject: Re: Semaphore assembly-code bug In-Reply-To: Message-ID: References: <417550FB.8020404@drdos.com> <1098218286.8675.82.camel@mentorng.gurulabs.com> <41757478.4090402@drdos.com> <20041020034524.GD10638@michonline.com> <1098245904.23628.84.camel@krustophenia.net> <1098247307.23628.91.camel@krustophenia.net> <20041029175527.GB25764@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 29 Oct 2004, Linus Torvalds wrote: > > Anyway, making "asmlinkage" imply "regparm(3)" would make the whole > discussion moot, so I'm wondering if anybody has the patches to try it > out? It requires pretty big changes to all the x86 asm code, but I do know > that people _had_ patches like that at least long ago (from when people > like Jan were playing with -mregaparm=3 originally). Maybe some of them > still exist.. Looking at just doing this for the semaphore code, I hit on the fact that we already do this for the rwsem's.. So changing just the regular semaphore code to use "fastcall" should fix this particular bug, but I'm still interested in hearing whether somebody has a patch for the system calls and faults too? Linus