From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: [PATCH] wire up support for the Alpha architecture Date: Mon, 14 Oct 2013 11:46:58 -0400 Message-ID: <20131014154658.GB9525@redhat.com> References: <20131010232132.GA27157@redhat.com> <20131011110419.GG14732@mudshark.cambridge.arm.com> <20131014150952.GH10491@mudshark.cambridge.arm.com> <20131014153916.GA8779@redhat.com> <20131014154338.GL10491@mudshark.cambridge.arm.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20131014154338.GL10491@mudshark.cambridge.arm.com> Sender: trinity-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Will Deacon Cc: Vince Weaver , "trinity@vger.kernel.org" On Mon, Oct 14, 2013 at 04:43:39PM +0100, Will Deacon wrote: > On Mon, Oct 14, 2013 at 04:39:16PM +0100, Dave Jones wrote: > > On Mon, Oct 14, 2013 at 04:09:52PM +0100, Will Deacon wrote: > > > > > Crikey, Alpha's syscall table is a right mess. > > > > I don't know anything about alpha, but does the kernel actually > > implement those OSF syscalls ? If not, it's unlikely we're going to > > implement them in trinity, so we could probably do the same thing we did on ia64, and > > > > #define SYSCALL_OFFSET 300 and skip all those ni_syscall entries. > > > > Or am I missing something ? > > Well, fork() is still syscall number 2, for example. I don't think we can > tidy this up with a simple offset unfortunately :( Ah, I missed that. Now I see why you said it was a mess. Ok, I'll apply your patch as is. thanks, Dave