From: Emmanuel Colbus <ecolbus@manux.info>
To: linux-kernel@vger.kernel.org
Subject: [RFC][3/11][MANUX] Kernel compatibility : syscall numbers
Date: Tue, 15 Apr 2014 15:42:51 +0200 [thread overview]
Message-ID: <534D375B.9070806@manux.info> (raw)
Continuing the discussion regarding syscalls, I have a question
regarding vector 0x80.
As I mentionned earlier, my OS's internals are very different from
Linux's, thus I have had a need for a few new syscalls. Since I wanted
to avoid any collision with Linux, but I also wanted to keep the
ability to put the syscall table in a single 4096-byte page on 64-bit
computers (on which I hope to run one day), I chose to start taking
syscall number 511, and to progress downwards - currently, I'm using
numbers 511 through 501 included (with a hole at 503, but I'll likely
fill it again in the future).
Is this okay for you? And in this case, if this isn't asking too much,
could you avoid using them for now, to avoid any conflict?
Thank you!
Emmanuel
next reply other threads:[~2014-04-15 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:42 Emmanuel Colbus [this message]
2014-04-15 15:02 ` [RFC][3/11][MANUX] Kernel compatibility : syscall numbers One Thousand Gnomes
2014-04-15 15:10 ` Emmanuel Colbus
2014-04-16 7:03 ` Clemens Ladisch
2014-04-16 10:23 ` Emmanuel Colbus
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=534D375B.9070806@manux.info \
--to=ecolbus@manux.info \
--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