From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 553DC679E7 for ; Fri, 28 Apr 2006 20:23:57 +1000 (EST) Subject: Re: [PATCH] Wire up *at syscalls From: David Woodhouse To: Paul Mackerras In-Reply-To: <17489.50396.320494.589703@cargo.ozlabs.ibm.com> References: <1145924011.16166.465.camel@shinybook.infradead.org> <17489.50396.320494.589703@cargo.ozlabs.ibm.com> Content-Type: text/plain Date: Fri, 28 Apr 2006 11:24:26 +0100 Message-Id: <1146219867.10561.39.camel@shinybook.infradead.org> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2006-04-28 at 17:31 +1000, Paul Mackerras wrote: > Nice idea, but you didn't change the syscall entry path to multiply > the syscall number by 24 instead of 16. Indeed. Neither did I wire up the spu callbacks. It wasn't meant to be applied as-is. > It would be nice to have a way to do something like that but generate > two separate tables instead of a single table with 3 entries per > syscall. Arnd apparently tried that once and it was icky. Perhaps we could do something like this though... .macro SPU adr .section .spu_callbacks,"a" .llong \adr .previous .endm -- dwmw2