Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263984AbTKJQgU (ORCPT ); Mon, 10 Nov 2003 11:36:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263985AbTKJQgU (ORCPT ); Mon, 10 Nov 2003 11:36:20 -0500 Received: from x35.xmailserver.org ([69.30.125.51]:43400 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S263984AbTKJQgJ (ORCPT ); Mon, 10 Nov 2003 11:36:09 -0500 X-AuthUser: davidel@xmailserver.org Date: Mon, 10 Nov 2003 08:35:11 -0800 (PST) From: Davide Libenzi X-X-Sender: davide@bigblue.dev.mdolabs.com To: Chris Friesen cc: Linux Kernel Mailing List Subject: Re: syscall numbers larger than 255? In-Reply-To: <3FAFB081.3090900@nortelnetworks.com> Message-ID: 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 Content-Length: 890 Lines: 26 On Mon, 10 Nov 2003, Chris Friesen wrote: > > Just a quick and simple question for someone that knows the answer. > > Stock 2.4.20 for i386 uses syscalls up to 252. I want to add about a > half-dozen new syscalls (forward porting stuff that we've got on 2.4.18). > > Does x86 support syscall numbers > 255? If yes, do I have to do > anything special to use them? If not, what are my options? Currently there's a discrepancy between include/asm-i386/unistd.h and arch/i386/kernel/entry.S. While the first define function numbers up to 252, the entry.S file fill up the table up to 258 (epoll crosses the 255 boundary :). - Davide - 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/