public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Sureshkumar Kamalanathan <skk@sasken.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to write System calls?
Date: Wed, 31 Oct 2001 12:35:54 +1100	[thread overview]
Message-ID: <15176.1004492154@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 29 Oct 2001 16:46:49 +0530." <3BDD3AA1.18FCC633@sasken.com>

On Mon, 29 Oct 2001 16:46:49 +0530, 
Sureshkumar Kamalanathan <skk@sasken.com> wrote:
>  I have 2.4.4 kernel.  I have to write some system calls for
>interaction with the kernel from the userland.  Can any of you tell me
>where I can get the information regarding this?  
>  I have the Linux Kernel Internals by Beck and others.  But it gives
>the procedure only for 2.2.x.
>  Moreover I need to implement these system calls as Loadable modules.

Syscall entries are hard coded into the syscall table, usually in
arch/$(ARCH)/entry.S.

There is no generic way to add a syscall that is serviced by a module.
I know that the modutils HOWTO gives examples of syscalls in modules
but that doc is out of date, on some architectures you have to adjust
additional registers to make a remote function call.  On those systems
the syscall table works because the kernel is compiled with special
flags, that will not work for modules.  Also Linus has said that he
does not want modules to be able to override syscalls.


  parent reply	other threads:[~2001-10-31 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 11:16 How to write System calls? Sureshkumar Kamalanathan
2001-10-30  9:11 ` Matthieu Delahaye
2001-10-31  1:35 ` Keith Owens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-30  9:25 Rajat Chadda

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=15176.1004492154@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skk@sasken.com \
    /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