From: Andi Kleen <ak@suse.de>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: syscall numbers larger than 255?
Date: 10 Nov 2003 16:54:10 +0100 [thread overview]
Message-ID: <p73d6c0rzh9.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <3FAFB081.3090900@nortelnetworks.com.suse.lists.linux.kernel>
Chris Friesen <cfriesen@nortelnetworks.com> writes:
> 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?
They should work fine on x86.
-Andi
next parent reply other threads:[~2003-11-18 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FAFB081.3090900@nortelnetworks.com.suse.lists.linux.kernel>
2003-11-10 15:54 ` Andi Kleen [this message]
2003-11-10 15:36 syscall numbers larger than 255? Chris Friesen
2003-11-10 15:58 ` Richard B. Johnson
2003-11-10 16:35 ` Davide Libenzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73d6c0rzh9.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox