kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: matthias.list@kaehlcke.net (Matthias Kaehlcke)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system call numbers
Date: Thu, 22 Nov 2012 10:19:36 +0100	[thread overview]
Message-ID: <20121122091936.GC3867@darwin> (raw)
In-Reply-To: <50ADE5F5.8020904@gmail.com>

Hi Matthias,

El Thu, Nov 22, 2012 at 09:44:37AM +0100 Matthias Brugger ha dit:

> I'm looking into the avr32 architecture implementation, as compiling the 
> kernel gives you several warnings about system calls which are missing.
> 
> I had a look in the unistd.h file I realized that system call numbers 
> differ widely from other architectures (I had a look at arm and x86).
> Are the system call numbers platform specific. As far as I understand, 
> the system calls are "wrapped" in libc. So I wonder if [g,e,uC]libc uses 
> a different system call number each architecture.
> A look in the source of uClibc didn't helped me to clear my doubts.

yes, the system call numbers are architecture specific

Documentation/ABI/stable/syscalls:

Note that this interface is different for every architecture
that Linux supports.  Please see the architecture-specific
documentation for details on the syscall numbers that are to
be mapped to each syscall

> If not all system calls are implemented for avr32:
> - is there a problem at all, or does libc implementation take care of 
> not implemented system calls?
> - if I want to add a system call, what are the steps needed?

there are several sources out there explaining this, one is
http://www.ibm.com/developerworks/library/l-system-calls/

best regards

-- 
Matthias Kaehlcke
Embedded Linux Developer
Amsterdam

            There is nothing so useless as doing efficiently
                 that which should not be done at all
                           (Peter Drucker)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

  reply	other threads:[~2012-11-22  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22  8:44 system call numbers Matthias Brugger
2012-11-22  9:19 ` Matthias Kaehlcke [this message]
2012-11-22  9:44 ` Adrian Perez de Castro

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=20121122091936.GC3867@darwin \
    --to=matthias.list@kaehlcke.net \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).