All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Colbus <ecolbus@manux.info>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][3/11][MANUX] Kernel compatibility : syscall numbers
Date: Wed, 16 Apr 2014 12:23:12 +0200	[thread overview]
Message-ID: <534E5A10.9040706@manux.info> (raw)
In-Reply-To: <534E2B4B.30801@ladisch.de>

Le 16/04/2014 09:03, Clemens Ladisch a écrit :
> Emmanuel Colbus wrote:
>> 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
> 
> ... you could just use another vector, such as 0x81.
> 
>> 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
> 
> These implementation details do not need to show up in the interface:
> 
> int syscall_0x81(int nr, ...)
> {
>     if (nr in range)
>         return table[511 - nr](...);
> }
> 
> 
> Regards,
> Clemens
> 

This would stop working as soon as I implemented any syscall/sysret or
sysenter/sysexit-like thing, as this technique has no notion of a
syscall vector.

Regards,

Emmanuel

      reply	other threads:[~2014-04-16 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 13:42 [RFC][3/11][MANUX] Kernel compatibility : syscall numbers Emmanuel Colbus
2014-04-15 15:02 ` One Thousand Gnomes
2014-04-15 15:10   ` Emmanuel Colbus
2014-04-16  7:03 ` Clemens Ladisch
2014-04-16 10:23   ` Emmanuel Colbus [this message]

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=534E5A10.9040706@manux.info \
    --to=ecolbus@manux.info \
    --cc=clemens@ladisch.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.