public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Colbus <ecolbus@manux.info>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][3/11][MANUX] Kernel compatibility : syscall numbers
Date: Tue, 15 Apr 2014 17:10:33 +0200	[thread overview]
Message-ID: <534D4BE9.5080805@manux.info> (raw)
In-Reply-To: <20140415160213.490439ea@alan.etchedpixels.co.uk>

Le 15/04/2014 17:02, One Thousand Gnomes a écrit :
> On Tue, 15 Apr 2014 15:42:51 +0200
> Emmanuel Colbus <ecolbus@manux.info> wrote:
> 
>> 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?
> 
> I don't see why the question arises. Your non Linux ABI binaries will be
> the ones to use such calls. They can have a different ELF header to Linux
> binaries. Linux then won't even try and run them by mistake. At that
> point your worst case is Linux calls eventually collide with your own and
> you have two tables according to ABI.

Hmmm... I see your point... Currently, I simply use the Linux ELF
header, and I hadn't even thought about using a different one. Indeed,
using a different header seems like a good solution.

OK, unless a better idea arises, I think I'll use this solution.

Thanks!

Emmanuel


  reply	other threads:[~2014-04-15 15:10 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 [this message]
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=534D4BE9.5080805@manux.info \
    --to=ecolbus@manux.info \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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