From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from terminus.zytor.com (terminus.zytor.com [192.83.249.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 01B7DDDEC6 for ; Sat, 10 Mar 2007 07:40:57 +1100 (EST) Message-ID: <45F1B818.4090007@zytor.com> Date: Fri, 09 Mar 2007 11:40:08 -0800 From: "H. Peter Anvin" MIME-Version: 1.0 To: Andi Kleen , David Woodhouse , akpm@osdl.org, linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, rmk@arm.linux.org.uk, sam@ravnborg.org, linux-arch@vger.kernel.org Subject: Re: [PATCH] Complain about missing system calls. References: <1173394873.3461.510.camel@pmac.infradead.org> <20070309163805.GV18564@lug-owl.de> In-Reply-To: <20070309163805.GV18564@lug-owl.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Jan-Benedict Glaw wrote: > > Not everybody has a simple indexed list of pointers :) For example, > for vax-linux, we use a struct per syscall with the expected number of > on-stack longwords for the call. > > So if something "new" is coming up, please keep in mind that it should > be flexible enough to represent that. :) > I discussed with Al Viro a while ago about using something like the SYSCALLS.def file from klibc as the source format for the system calls. That would deal very flexibly with almost all kinds of stub generation. -hpa